Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(x-posts): add the metaplex-mcp, sperax-staking, and avatar-launch drafts
nirholas483bdf83c6c2
diff --git a/docs/x-posts/README.md b/docs/x-posts/README.mdnew file mode 100644index 000000000..71b5703bc--- /dev/null+++ b/docs/x-posts/README.md@@ -0,0 +1,63 @@+# X post drafts++Ready-to-paste X (Twitter) announcement copy and the video prompts that go with it. Internal+staging only: nothing here is posted automatically, and posting is owner-gated per+[`CLAUDE.md`](../../CLAUDE.md) (`git push` / publishing / posting to external channels needs+explicit approval). Each file states what it's for and what has already been verified true.++## How these are written++- **Paste-ready, not outlines.** No placeholders, no "insert link here". Every link in a draft+ resolves today.+- **Character counts are measured, not guessed**, against X's rule that any URL counts as 23+ characters regardless of length. Where a draft states a count, it was computed.+- **Each file opens with a verified-claims block** and, where it matters, a "do not claim" list.+ That list is the useful part: it records what someone could disprove in ten minutes.+- **No em-dashes and no emoji**, matching the repo's writing rules.++## Product and infrastructure launches++| File | What it announces |+| --- | --- |+| [`onchain-agent-wallets-x-post.md`](onchain-agent-wallets-x-post.md) | Agent wallets with an on-chain spending allowance instead of a private key: SPL Token delegation, guardrails, x402, revocable custody |+| [`mcp-registry-fleet-x-post.md`](mcp-registry-fleet-x-post.md) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |+| [`metaplex-agent-mcp-launch.md`](metaplex-agent-mcp-launch.md) | The open-source agent infrastructure announcement covering `@three-ws/metaplex-agent-mcp` and `@three-ws/onchain-agent-wallets`, and why the integrations are bullish for $THREE |+| [`metaplex-agent-mcp-x-post.md`](metaplex-agent-mcp-x-post.md) | The MCP server that mints an agent into the Metaplex Agent Registry with its own wallet and EIP-8004 identity |+| [`metaplex-agent-deployer-x-post.md`](metaplex-agent-deployer-x-post.md) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |+| [`3d-ar-studio-launch.md`](3d-ar-studio-launch.md) | 3D AR Studio, the AR studio extracted from three.ws and published as an open-source package |+| [`ar-quick-look-fix-x-post.md`](ar-quick-look-fix-x-post.md) | AR Forge and AR Studio now open real Apple Quick Look / Google Scene Viewer on a phone, matching what `/avatars/:id/ar` already did. Shipped to `main` locally, **not yet deployed**: do not post until verified live on a real iPhone |+| [`threews-avatar-launch.md`](threews-avatar-launch.md) | The three.ws avatar pipeline launch copy |+| [`oracle-trading-mcp-x-post.md`](oracle-trading-mcp-x-post.md) | The oracle trading MCP server launch |+| [`sperax-staking-in-chat-x-post.md`](sperax-staking-in-chat-x-post.md) | SperaxOS chat-native staking, balance, and buy-SPA tool calls. The embedded `/staking` page is not working yet: do not announce until the blockers in the file clear |+| [`news-archive-x-post.md`](news-archive-x-post.md) | The news archive |+| [`pumpfun-article-x-post.md`](pumpfun-article-x-post.md) | The pump.fun article |++## Video and narration scripts++| File | What it covers |+| --- | --- |+| [`metaplex-agent-mcp-veo-script.md`](metaplex-agent-mcp-veo-script.md) | Shot-by-shot Veo (image-to-video) prompts for the agent infrastructure clip, built from a three.ws 3D avatar as the reference frame |+| [`metaplex-agent-deployer-video-script.md`](metaplex-agent-deployer-video-script.md) | Spoken narration for the deployer clip |+| [`threews-avatar-video-script.md`](threews-avatar-video-script.md) | Shot list for the avatar clip |+| [`3d-ar-studio-video-script.md`](3d-ar-studio-video-script.md) | Narration and shot prompts for the AR Studio launch video |++## Events and community++| File | What it covers |+| --- | --- |+| [`event-x-posts.md`](event-x-posts.md) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |+| [`x-meetup-posts.md`](x-meetup-posts.md) | The in-platform community meetup announcement |+| [`ibm-skillsbuild-x-post.md`](ibm-skillsbuild-x-post.md) | The IBM SkillsBuild badge |+| [`fomo-verified-x-post.md`](fomo-verified-x-post.md) | FOMO verification |++## Conventions++Posting is manual and owner-gated. **X delivery of the changelog is retired** (owner directive+2026-07-18): `scripts/changelog-x.mjs` still exists but no cron calls it, so nothing in this folder+is on an automated lane. Treat every file here as copy waiting for a human to send.++Not registered in `data/pages.json`, and doesn't need to be: `scripts/audit-docs.mjs` only checks+direct `docs/*.md` files for a page entry, not files under a `docs/` subdirectory, so a nested+folder like this one is the convention for internal drafts that shouldn't be crawlable. When a+draft moves in here from the top level, drop its slug from `UNPUBLISHED_DOCS` in that script: the+entry is dead once the file is no longer routed.diff --git a/docs/x-posts/metaplex-agent-mcp-launch.md b/docs/x-posts/metaplex-agent-mcp-launch.mdnew file mode 100644index 000000000..ea02f5cc3--- /dev/null+++ b/docs/x-posts/metaplex-agent-mcp-launch.md@@ -0,0 +1,171 @@+# X post: the agent wallet + on-chain deploy stack is open source++Announcement copy for open-sourcing the infrastructure that's been running three.ws agent wallets:++- [**@three-ws/onchain-agent-wallets**](https://github.com/nirholas/three.ws/tree/main/packages/onchain-agent-wallets):+ gives an agent a Solana wallet as a capped spending allowance, not a private key. Guardrails+ (per-tx cap, daily cap, allowlists, expiry, pause), x402 payments, owner keeps custody.+- [**@three-ws/metaplex-agent-mcp**](https://github.com/nirholas/metaplex-agent-mcp): mints an+ agent onto Solana with its own on-chain wallet and an EIP-8004 identity in the Metaplex Agent+ Registry, in one command.++**Thesis (owner framing, 2026-08-19):** three.ws already had agent wallets, and people know it.+That's not the news. The news is that the infrastructure is now open source, so any developer, any+project, can give their own agents the same thing: a wallet, an identity, and x402 payments,+without building it themselves. That's bullish for $THREE specifically because it's not just+three.ws users deploying agents anymore, it's every project that plugs into this stack, and every+deploy pays a fee that funds $THREE buybacks. Lead with the open-source/developer angle, not "an+agent has a wallet" (old news, less bullish) or a mint-drop framing (wrong thesis entirely, no+supply/collection talk).++**Verified true today** (shipped code, checked against mainnet): `metaplex-agent-mcp` is at 0.2.0+on npm and in the official MCP registry (`io.github.nirholas/metaplex-agent`); a mainnet deploy+through it costs ~0.007 SOL rent plus a 0.02 SOL fee paid to the wallet the $THREE buyback lane+spends from, halved at 50,000 $THREE held in the paying wallet and waived at 250,000, free on+devnet; keys never leave the client either way (agent's own key, or Phantom/Solflare/Backpack/+Ledger). `onchain-agent-wallets` is live and published, funds sit in a vault the owner controls, the+agent holds a capped SPL Token delegation the token program itself enforces on-chain.++**One thing to NOT claim:** that $THREE buybacks are running right now. The fee lane is wired and+funded, but `buyback.enabled` is currently `false` on the public ledger+([`/api/three-token/stats`](https://three.ws/api/three-token/stats)), and someone will check.+"Every deploy funds $THREE buybacks" is true and safe. "We are buying back $THREE right now" is+not, until that flag flips.++---++## 1. Main post (recommended): open source, developer-focused++> We open-sourced our agent wallet + on-chain deploy + x402 stack.+>+> Any project can now give their agents a Solana wallet, an EIP-8004 identity, and payment rails in+> one command. No account, no server.+>+> Every deploy through it funds $THREE buybacks.+>+> github.com/nirholas/metaplex-agent-mcp++Why this one: it doesn't re-announce something people already know (three.ws agents have wallets).+It announces that the *infrastructure* is now anyone's to build on, which is the actually-new,+actually-bullish fact. The last line is the whole investment thesis in six words.++## 1b. Alternate: sharper on the mechanism++> Just open-sourced the agent wallet stack that's been running on three.ws.+>+> `npx @three-ws/metaplex-agent-mcp` gives any project on-chain wallets, identity, and x402+> payments for their agents. One command, self-custodial, MCP-native.+>+> Every project that builds on it becomes a $THREE buyer.+>+> github.com/nirholas/metaplex-agent-mcp++The line to protect in any edit: **"every project that builds on it becomes a $THREE buyer."**+That's the actual bull case, stated plainly: this isn't three.ws's own deploy volume, it's every+other project's users too, compounding.++## 1c. Alternate: tightest cut++> We open-sourced the infrastructure behind three.ws agent wallets.+>+> Any developer, any project, can now give their agents a real Solana wallet + on-chain identity ++> x402 payments. One command.+>+> Every integration is a $THREE buyer, forever.+>+> github.com/nirholas/metaplex-agent-mcp++## 2. Superseded framing (kept for reference, not recommended)++Drafted before the open-source/developer reframe. Still technically accurate, but leads with+"your agent has a wallet," which the owner correctly flagged as old news for anyone who already+knows three.ws, and it undersells the actual story.++> Your agent can now hold its own wallet.+>+> One command and it deploys itself into the Metaplex Agent Registry on Solana: its own on-chain+> wallet, an EIP-8004 identity, x402 on.+>+> The 0.02 SOL deploy fee buys $THREE. Hold 250k and you deploy free, forever.+>+> github.com/nirholas/metaplex-agent-mcp++## 3. Thread (use if the main post lands)++**1/**+> We open-sourced the agent wallet + on-chain deploy stack that's been running on three.ws.+>+> Any project can now give their agents the same thing: a Solana wallet, an on-chain identity, and+> x402 payments. One command, self-custodial.+>+> Here's what shipped. 🧵++**2/**+> Two pieces, both real, both open source today.+>+> **onchain-agent-wallets**: an agent gets a Solana wallet as a capped spending allowance, not a+> key. **metaplex-agent-mcp**: an agent gets minted on-chain with its own identity in the Metaplex+> Agent Registry.++**3/**+> The wallet piece: your money stays in a vault YOU own. The agent gets a delegation with a+> ceiling, and the Solana token program itself refuses any spend past it, no matter how the agent+> is prompted. Per-tx caps, daily caps, allowlists, a pause switch. Revocable in one instruction.++**4/**+> The identity piece: mint a Metaplex Core asset, register an EIP-8004 identity, done. The agent+> gets its own on-chain wallet (the asset's own signer, not one you made and named after it) and+> shows up in the Metaplex Agent Registry with a portable, publicly-readable identity.++**5/**+> Both speak x402. An HTTP 402 comes back with a price, the agent checks it against its+> guardrails, pays, gets the response. No key sharing, no invoice, no human in the loop for a+> $0.001 call.++**6/**+> Custody is the part we refused to compromise on, in both packages. Agents sign with their own+> keypair or a capped delegation, never a raw key with no ceiling. Owner actions come back as+> unsigned transactions for Phantom, Solflare, or a Ledger. Nothing custodial on our servers, ever.++**7/**+> Now the part that makes this pay for itself.+>+> A mainnet deploy through metaplex-agent-mcp costs 0.02 SOL on top of rent. That fee goes to the+> wallet the $THREE buyback lane spends from. Deploys fund buybacks. That's the business model.++**8/**+> And holding $THREE is how you stop paying it.+>+> 50,000 $THREE in the paying wallet halves the fee. 250,000 waives it. Read live from the chain+> when the transaction is built. Nothing staked, nothing locked. Hold the tokens, deploy your whole+> fleet free.++**9/**+> This is why open-sourcing it is bullish, not just generous: every project that plugs into this+> stack sends deploy fees to $THREE buybacks. Not just our users. Anyone's.++**10/**+> Works in any MCP client:+>+> ```+> claude mcp add metaplex-agent -- npx -y @three-ws/metaplex-agent-mcp+> claude mcp add onchain-agent-wallets -- npx -y @three-ws/onchain-agent-wallets+> ```+>+> Or skip the install and deploy from the browser.++**11/**+> Open source. Real programs, real Solana, no mocks.+>+> github.com/nirholas/metaplex-agent-mcp+> github.com/nirholas/three.ws/tree/main/packages/onchain-agent-wallets++## 4. Reply-slot copy (post as first reply to the main post)++Use this to carry the second link and the browser path without spending the main post's one+outbound slot.++> The wallet half of this is @three-ws/onchain-agent-wallets, a capped spending allowance+> enforced by the Solana token program itself, not a raw key. And if you just want to see the+> deploy: the browser version builds the transaction locally, your wallet signs it, nothing+> touches a server.diff --git a/docs/x-posts/metaplex-agent-mcp-veo-script.md b/docs/x-posts/metaplex-agent-mcp-veo-script.mdnew file mode 100644index 000000000..1858d3cbd--- /dev/null+++ b/docs/x-posts/metaplex-agent-mcp-veo-script.md@@ -0,0 +1,104 @@+# Veo script: the open-source stack++Shot-by-shot **visual** prompts for a Veo image-to-video clip to run alongside+[`metaplex-agent-mcp-launch.md`](metaplex-agent-mcp-launch.md). Text-to-video only, no dialogue, no+voiceover: the reference frame is a three.ws 3D avatar, and every prompt below is written to be+pasted straight into Veo as-is.++**Reference image:** a three.ws avatar render, front-facing, neutral pose, transparent or dark+background gives Veo the cleanest key. Use the exact same reference image across every shot, or the+character drifts between clips.++**Direction rules**++1. **No on-screen text you care about.** Generative video mangles letters. Keep every address,+ number, and label as an abstract glyph in the render, and comp real text in afterwards.+2. **One idea per shot.** A shot that tries to do two things reads as a mess at 8 seconds.+3. **Camera does one move per shot.** Slow. The subject moves, not the operator.+4. **Palette:** deep near-black background, Solana violet and teal accents, one warm gold for value+ in motion. Nothing else.++The visual metaphor here is **closed → open-sourced → replicates → funds one thing that grows**:+this is the open-source/infra announcement, not a generic "an agent deploys" clip, so the arc has+to show something spreading to others, not just one agent getting a wallet.++---++## Single hero clip (8s, use this if you only render one)++> Cinematic 3D product shot, near-black void studio. The humanoid agent from the reference image+> stands center frame, encased in a faceted violet crystal shell, like something kept behind glass.+> A hairline crack runs down the shell from top to bottom. The shell shatters outward in slow+> motion, fragments dissolving into light before they travel far, revealing the agent already+> glowing from within, threads of violet light running under its skin like circuitry. As the last+> fragment fades, a small hexagonal token of warm gold light ignites in its open palm. Camera: slow+> push in from wide to medium, ending at chest height. Lighting: soft key upper left, violet rim+> light from behind, gold bounce from the palm onto the face. Shallow depth of field, fine film+> grain, subtle volumetric haze. Audio: a held tense drone that breaks on the shatter into a bright+> resonant chime, then settles into a low steady pulse. No text, no logos, no people.++## Four-shot sequence (8s each, cut together to ~32s)++**Shot 1 of 4: the shell breaks**++> Cinematic 3D render, near-black void. The agent from the reference image stands encased in a+> faceted violet crystal shell. A crack forms and the shell shatters outward, fragments dissolving+> into light. Underneath, the agent is already glowing softly from within. Camera: slow dolly in,+> wide to medium. Lighting: violet rim from behind, soft key upper left. Audio: tense drone breaking+> into a bright chime. No text.++**Shot 2 of 4: it replicates**++> Same void. Behind the agent, faint violet outlines of other humanoid silhouettes begin resolving+> out of the darkness, one by one, in a loose arc, each catching the same internal glow the first+> one has. None of them are identical: subtle variation in each silhouette's build and stance. The+> original agent turns slightly, as if aware of them. Camera: slow orbit right, keeping the original+> agent in the foreground, sharp, while the others resolve soft-focus behind. Lighting: violet+> spreading outward from the center figure. Audio: the chime repeating faintly, staggered, like an+> echo catching on.++**Shot 3 of 4: every one lights a palm**++> Wide shot, the full arc of now-solid humanoid silhouettes, the original agent still sharpest in+> the center. In one continuous beat, a small gold token of light ignites in each figure's open+> palm, left to right across the arc, like a wave. Threads of gold light begin drifting from every+> palm toward a single point above and behind the group. Camera: slow lateral track following the+> wave of gold ignitions. Lighting: violet fill, warm gold accumulating overhead. Audio: a cascade+> of soft chimes following the wave, building under a rising low tone.++**Shot 4 of 4: it becomes one light**++> Camera pulls back and up fast, revealing the gold threads from every figure converging into a+> single bright point far above the group, which pulses once, hard, like a heartbeat, and sends a+> ring of light rippling back down across all of them. The group stands still, lit gold, small+> against the dark. Camera: fast pull back to a wide, then hold. Lighting: single overhead point+> light, violet ambient below. Audio: bass drop on the pulse, long reverberant tail, fading to near+> silence.++## Negative prompt (paste into the negative field on every shot)++> text, letters, numbers, words, subtitles, watermark, logo, UI, user interface, HUD, charts,+> coins, dollar signs, crowds of identical characters, warped hands, extra fingers, face morphing,+> shaky camera, jump cuts, lens flare spam, rainbow colors, low resolution, cartoon shading++## Reading the metaphor++- **Shot 1** (locked away) is the "before": powerful, but closed, only usable by whoever built the+ shell.+- **Shot 2 → 3** (replication, simultaneous ignition) is the actual news: it's open source now, and+ it isn't just the original agent anymore, others get the same thing without anyone building it+ for them again. This is the beat to protect if the clip has to be cut down; it's the one part a+ generic "one agent deploys" clip cannot say.+- **Shot 4** (every thread feeding one point) is the $THREE payoff: all of that activity, spread+ across many agents and many projects, converges on one thing.++## Post-production++- End card, 2 seconds, static: the repo link on black. Nothing else.+- Cut to land on the beat where the palms ignite in shot 3, that's the moment the "it spreads"+ idea is legible, and it's what a muted autoplay timeline shows first.+- Post as native video, not a link to a video. X doesn't show a preview card and the video at the+ same time, and the video wins every time.+- If you want a version that ends on something you can comp a logo or link over cleanly, replace+ shot 4's fast pull-back with a static hold on the single overhead light point, flat dark+ background, nothing moving in frame.diff --git a/docs/x-posts/sperax-staking-in-chat-x-post.md b/docs/x-posts/sperax-staking-in-chat-x-post.mdnew file mode 100644index 000000000..8f5ff4555--- /dev/null+++ b/docs/x-posts/sperax-staking-in-chat-x-post.md@@ -0,0 +1,99 @@+# X post: staking, balance, and buy SPA inside SperaxOS chat++Announcement copy for the new `/staking` surface on `chat.sperax.io` and the chat-native staking+tool calls (stake, unstake, extend lock, check balance, buy SPA) wired into the assistant.++**Thesis of this announcement:** you no longer need to leave the chat to manage your SPA position.+Ask the assistant to stake, check your balance, or buy SPA, and it runs as a real, guarded on-chain+call, not a redirect to a separate dApp.++**This is a two-part feature, and the two parts are in different states right now. Read this+section before picking a post to publish.**++## Part 1: chat-native staking tool calls, shipped and true today++Verified against the merged code (`88a3684` on `main`, live on `chat.sperax.io`):++- Asking the assistant to stake SPA, unstake, extend a veSPA lock, check balance, mint/redeem USDs,+ or buy SPA routes through real, guarded tool calls, not mocked responses.+- `stakeSpa`, `unstakeSpa`, `increaseStake`, `extendStake` are registered across every wiring+ surface (renders, inspectors, DeFi Guard mutating-API gate, keyword routing) so they render with+ a proper UI card and require the same risk confirmation as any other fund-moving action.+- SPA and USDs are in the Arbitrum token allowlist for the swap tool, so "buy SPA with USDC" works+ without depending on a remote tokenlist refresh.+- "buy spa", "stake spa", "unstake spa" are recognized keyword triggers, so the natural-language+ phrasing works without needing exact tool names.++**This part is safe to announce now.**++## Part 2: the embedded `/staking` page (full app.sperax.io experience in an iframe), NOT ready++The `/staking` page exists, is reachable from the sidebar, and matches SperaxOS's design language.+But the embedded app.sperax.io view inside it does not load yet:++1. `app.sperax.io` returns Cloudflare's managed-challenge 403 to the iframe request, and separately+ sends `X-Frame-Options: SAMEORIGIN`, which refuses to be framed by `chat.sperax.io` at the+ browser level. Both need a Cloudflare zone-level fix (response header transform ++ challenge-skip rule) on `app.sperax.io`, not yet applied.+2. `chat.sperax.io`'s own CSP `frame-src` directive does not yet include `app.sperax.io`. Code fix+ pending, blocked on repo access as of this writing.+3. The wallet connector on the live `chat.sperax.io` build has a corrupted+ `NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID` from an unrelated 2026-08-06 deploy incident, so even once+ framing is unblocked, WalletConnect will not work until that value is set correctly and the+ image is rebuilt.++**Do not publish a post claiming "the full app.sperax.io experience is in chat" until all three of+the above are resolved and independently verified with a real browser load, not just an HTTP+status check.** Once fixed, a short follow-up post ("now you can see your full position, not just+the tool card") is a good second post, not a rewrite of the first.++---++## 1. Main post (recommended, publish now)++Leads with the thing that actually works: talking to the assistant.++> You don't need a separate tab to manage your SPA position anymore.+>+> Tell SperaxOS to stake, check your balance, or buy SPA, and it runs as a real on-chain call, with+> the same risk checks as everything else in chat.+>+> chat.sperax.io++Why this one: it makes a concrete, checkable claim ("tell it to stake") instead of a vague platform+claim, and it doesn't reference the embed, which isn't ready.++## 2. Alternate: example-led++> "stake 500 SPA for 6 months"+> "what's my SPA balance"+> "buy SPA with USDC"+>+> All three now run inside SperaxOS chat as real transactions. No new tab, no separate dApp.+>+> chat.sperax.io++Why this one: the three example prompts are copy-pasteable and match the actual hint text shipped+on the `/staking` page footer, so anyone who tries it gets exactly what the post promised.++## 3. Alternate: short/punchy++> Staking, balance checks, and SPA buys now live inside the SperaxOS chat itself.+>+> Ask. It runs. No context switch.++---++## Notes on framing++- **Do not mention $THREE.** This is a Sperax/SPA-specific feature on a Sperax product. Keep the two+ ecosystems separate in copy.+- **Do not claim the embedded app.sperax.io iframe view works.** See Part 2 above. Posting that+ claim before the Cloudflare + CSP + WalletConnect fixes land and are verified in a real browser+ will read as false the moment someone clicks through, since the iframe currently renders a+ broken-content icon.+- **"Real on-chain call, not a redirect" is the phrase doing the work.** SperaxOS has had chat+ before; what's new is that these specific actions are wired as guarded tool calls rather than+ just being informational.+- Update this file (or add a dated addendum below) once Part 2 is verified fixed, so the "NOT ready"+ section doesn't go stale and mislead a future poster.diff --git a/docs/x-posts/threews-avatar-launch.md b/docs/x-posts/threews-avatar-launch.mdnew file mode 100644index 000000000..0157053da--- /dev/null+++ b/docs/x-posts/threews-avatar-launch.md@@ -0,0 +1,55 @@+# Give your AI a body: the avatar film++X copy for the platform film. The shot prompts that produce the video live in+[threews-avatar-video-script.md](./threews-avatar-video-script.md).++**Thesis:** the tagline, literally. A model with no form gets one, the form moves, the form holds+its own wallet, the form walks out into the real world. Nothing about supply, price, or buybacks.++**Verified true today:** prompt-to-avatar produces a rigged, animatable body; the avatar renders and+animates in the browser; agents carry their own Solana wallet address; `<agent-3d>` embeds an avatar+on any page with a script tag and one element. **Do not claim** that $THREE buybacks are executing.++All three posts below are inside 280 characters with X's 23-character URL count, so they post from+any account, Premium or not.++## X post++### Recommended++> Give your AI a body.+>+> Type a prompt, get a rigged 3D avatar that talks, walks, and holds its own Solana wallet. Drop it+> on your site with one tag.+>+> three.ws++Line 1 is the product in five words. Line 2 is the three things that make it different from a+picture, in the order people care about. The wallet lands last because it is the part nobody expects+from an avatar company.++### Alternate: builder-facing++> Your agent has a voice, a model, and a name. It still has no body.+>+> three.ws gives it one: a rigged 3D avatar you can talk to, embed anywhere with a single element,+> and fund with its own on-chain wallet.+>+> ```html+> <script type="module" src="https://three.ws/agent-3d/latest/agent-3d.js"></script>+> <agent-3d src="agent://base/42"></agent-3d>+> ```++### Alternate: $THREE-first++> Every 3D agent built on three.ws ships with its own Solana wallet, an on-chain identity, and+> pay-per-call built in.+>+> $THREE is the coin of that economy.+>+> Give your AI a body: three.ws++### Reply slot, post under the main one++> The avatar in the video was generated from a text prompt on three.ws, rigged automatically, and+> rendered in the browser. No modeling, no rigging software, no download.