Skip to content

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.

docs(announcements): draft announcement packs for Walk and the $THREE token MCP server

nirholas9fba13a71ec5
diff --git a/docs/announcements/three-token-mcp.md b/docs/announcements/three-token-mcp.md
new file mode 100644
index 000000000..ae8c7759c
--- /dev/null
+++ b/docs/announcements/three-token-mcp.md
@@ -0,0 +1,130 @@
+# Announcement pack: the $THREE token MCP server
+
+**Surface:** [`@three-ws/three-token-mcp`](https://www.npmjs.com/package/@three-ws/three-token-mcp) ·
+**Ledger key:** `@three-ws/three-token-mcp` · **Stage:** drafted · **Published to npm:** 1.1.3 is `latest`
+· **Announced externally:** never
+
+Listed as never announced in [the coverage audit](../announcement-coverage.md), which flags it as the
+$THREE-native post that "writes itself". Token topic is the account's highest measured lift (13.3x),
+and this is a feature that genuinely touches the token rather than mentioning it. Written against
+[the announcement voice](../announce-voice.md).
+
+---
+
+## The claim, and where it is checked
+
+> An MCP server that lets an AI assistant burn $THREE on Solana. Its burn tool is declared
+> irreversible to the client, and by default the server refuses to sign until the call carries
+> `confirm: true`.
+
+| Part of the claim | Where it is real |
+|---|---|
+| It is a published MCP server anyone can run | `npm view @three-ws/three-token-mcp` returns 1.1.3 as `latest` (4 versions, Apache-2.0, maintainer `three-ws`). Running `npx -y @three-ws/[email protected]` over stdio on 2026-09-17 answered `initialize` as `three-token-mcp` 1.1.3 and `tools/list` with exactly `three_price`, `three_balance`, `three_burn`. |
+| It burns $THREE on Solana | [`packages/three-token-mcp/src/lib/token.js`](../../packages/three-token-mcp/src/lib/token.js) `burnThree()` builds one Solana mainnet transaction (SPL transfer per leg plus a memo), signs, sends, and confirms. The live catalog detail reads "signs and broadcasts on Solana mainnet". |
+| It can only ever burn $THREE | `assertCanonicalThree()` in the same file refuses to sign unless the mint served by `/api/token/config` equals `THREE_MINT` in [`src/config.js`](../../packages/three-token-mcp/src/config.js) (`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`). Not in the post, but it is why the post is safe to make. |
+| Flagged irreversible | `annotations: { readOnlyHint: false, destructiveHint: true, ... }` in [`src/tools/three-burn.js`](../../packages/three-token-mcp/src/tools/three-burn.js). The public [MCP Tool Catalog](https://three.ws/mcp-tools?server=three-token-mcp) classifies it as **Irreversible** ("Cannot be undone once it runs.") and the two reads as **Read-only**; that page is generated from tool source, so the label cannot drift. |
+| By default it will not sign without `confirm: true` | The handler in `three-burn.js` returns `confirmation_required` before `burnThree()` is ever called when `REQUIRE_CONFIRM && confirm !== true`, and `REQUIRE_CONFIRM` in `config.js` is `true` unless the operator sets it to `0`/`false`. Confirmed live: a `three_burn { usd: 1 }` call against the published 1.1.3 package came back `"error": "confirmation_required"` with nothing signed. |
+| Where the burned tokens go | The burn leg routes to the Solana incinerator (`1nc1nerator11111111111111111111111111111111`). `computeSplit()` sends the rest to the treasury only when the live config has one; `/api/token/config` currently serves `"treasury": null`, so today a burn sends 100% to the incinerator. This is why the post says "burn" and does not promise a treasury split. |
+
+Full mechanism: [`packages/three-token-mcp/README.md`](../../packages/three-token-mcp/README.md);
+install lines for every three.ws server: [docs/mcp.md](../mcp.md).
+
+## Media
+
+Captured from the live route by `npm run announce:media` against the recipe below. Provenance
+(route, commit, time, sha256) lands in
+[`public/announce/media-manifest.json`](../../public/announce/media-manifest.json).
+
+| Shot | File | Notes |
+|---|---|---|
+| `three-token-mcp-hero` | `/announce/img/three-token-mcp-hero.webp` | 1800x1013, signed out. The MCP Tool Catalog filtered to this server: the "Let your assistant run the safe ones by itself" policy with its Strict, Balanced and Open profiles, then the server's three tools with `three_burn` badged Irreversible and the two reads badged Read-only. |
+
+**Alt text, required on the post:**
+
+> The three.ws MCP Tool Catalog filtered to the @three-ws/three-token-mcp server: 3 of 321 tools,
+> with three_balance and three_price labelled read-only and three_burn labelled irreversible, all free
+
+What the recipe frames out, and why. The catalog's tool subtitles and descriptions name the
+third-party price source the tools quote from, which would put another crypto project into a
+committed frame; they are hidden (`.mc-title`, `.mc-desc`), leaving each tool's name and its safety
+and price badges, which are the subject. The policy snippet block (`.mc-policy-out`) is hidden so the
+profiles and the three tools fit one 16:9 frame. Nothing is restaged: every badge, count and label is
+what the live page rendered.
+
+The two existing `three-token-hero` and `three-token-trades` shots already carry this package as
+their surface, and were checked before this one was captured. They were not reused: they frame
+`/three-token`, show no part of the MCP server, were captured 2026-09-04 with a price that no longer
+matches the live page, and carry third-party venue buttons in the frame.
+
+## The post
+
+Pattern: mechanism lead. **179 weighted characters** by `post-tweet.mjs` (which counts the bare
+link at its real 41 characters; X itself counts it as 23, so it lands near 161 on the platform),
+inside the 100 to 179 band. Tags `@solana` because the burn is a Solana mainnet transaction and
+$THREE is an SPL token.
+
+Postable file: [`three-token-mcp.post.txt`](./three-token-mcp.post.txt).
+
+```text
+An MCP server that lets an AI burn $THREE on @solana. three_burn is flagged irreversible and by default won't sign without confirm: true. three.ws/mcp-tools?server=three-token-mcp
+```
+
+Ship it with `three-token-mcp-hero` attached and the alt text above.
+
+### Why it is written that way
+
+A token burn tool invites two readings: a gimmick, or a foot-gun that lets a model spend your
+wallet. The second is the objection a developer actually raises, so the post answers it inside
+the mechanism instead of hyping the first. "Flagged irreversible" is the MCP annotation clients
+use to decide whether to prompt; "won't sign without confirm: true" is the server-side gate that
+holds even against a client that ignores the annotation. Both are checkable in the linked page.
+
+`@AnthropicAI` was considered (MCP is their protocol, and the voice guide allows the tag for an
+MCP server) and left off: the post already carries the tag the mechanism depends on, and a second
+tag spends characters the band does not have. The `npx` line is not in the post on purpose: X
+would parse `@three-ws` in `@three-ws/three-token-mcp` as a mention of an account we do not own.
+The linked catalog entry carries the exact install command.
+
+Cut to hold the band, all true and all in the Telegram variant: the canonical-mint assertion, the
+default $100 per-burn cap, and the two read-only tools.
+
+## Telegram variant
+
+```text
+The $THREE token now has its own MCP server, and it has never been posted about.
+
+npx -y @three-ws/three-token-mcp
+
+Any MCP client (Claude Code, Claude Desktop, Cursor) gets three tools:
+
+- three_price: the live USD price of $THREE, and how much $THREE a USD amount buys. Read-only.
+- three_balance: the $THREE and SOL balance of any Solana wallet. Read-only.
+- three_burn: burns a USD amount of $THREE your wallet already holds, in one Solana transaction.
+
+The burn is built to be hard to misuse:
+
+- It is flagged irreversible, so clients that honour MCP annotations ask you before it runs.
+- The server itself refuses until the call carries confirm: true, whatever the client does.
+- Each burn is capped at $100 by default (MAX_BURN_USD).
+- Before signing, it checks the token is the canonical $THREE mint, so a bad config can never
+ point it at another token.
+
+See all three tools and their safety labels: three.ws/mcp-tools?server=three-token-mcp
+```
+
+## Changelog
+
+**No new entry.** The package shipped with the 2026-06-13 entry ("All 14 three.ws MCP servers are
+now live on npm and the official MCP registry"). This pack announces an existing package externally
+for the first time; it ships nothing new.
+
+## Posting
+
+Publishing to an external channel is owner-gated under the operating rules, every time. Nothing in
+this pipeline posts. The queue item is `three-token-mcp` (status `review`, lane `token`, pattern
+`mechanism`); preview with:
+
+```bash
+node scripts/post-tweet.mjs --file docs/announcements/three-token-mcp.post.txt --dry-run
+npm run x:content -- run --dry-run --id three-token-mcp
+```
diff --git a/docs/announcements/three-token-mcp.post.txt b/docs/announcements/three-token-mcp.post.txt
new file mode 100644
index 000000000..26034e341
--- /dev/null
+++ b/docs/announcements/three-token-mcp.post.txt
@@ -0,0 +1 @@
+An MCP server that lets an AI burn $THREE on @solana. three_burn is flagged irreversible and by default won't sign without confirm: true. three.ws/mcp-tools?server=three-token-mcp
\ No newline at end of file
diff --git a/docs/announcements/walk.md b/docs/announcements/walk.md
new file mode 100644
index 000000000..47d866102
--- /dev/null
+++ b/docs/announcements/walk.md
@@ -0,0 +1,112 @@
+# Announcement pack: Walk, the one-tag walking avatar
+
+**Surface:** [`/walk`](https://three.ws/walk) · **Ledger key:** `/walk` · **Stage:** drafted
+· **Shipped:** 2026-06-21 · **Announced externally:** never as a surface post
+
+Sitemap priority 0.8. The `/walk` landing and its one-tag embed have not had their own announcement
+pack. Written against [the announcement voice](../announce-voice.md).
+
+---
+
+## The claim, and where it is checked
+
+> Paste one iframe tag on any site and a rigged 3D avatar walks there, in one of six built-in
+> worlds chosen with a query parameter. There is no SDK to install and no build step.
+
+Verified by reading the code and the live page on 2026-09-17:
+
+| Part of the claim | Where it is real |
+|---|---|
+| One iframe tag | The page's own snippet is a single `<iframe src="https://three.ws/walk-embed?env=void&autoplay=true">` ([`pages/walk-landing.html`](../../pages/walk-landing.html)); the live page reads "One tag. Any site." and "Paste the iframe". |
+| On any site | `vercel.json` serves `/walk-embed` with `content-security-policy: frame-ancestors *` and `cross-origin-resource-policy: cross-origin`; `curl -sI https://three.ws/walk-embed` returned that header on 2026-09-17. |
+| A rigged 3D avatar that walks | [`src/walk-embed.js`](../../src/walk-embed.js) loads a humanoid GLB (`/avatars/default.glb`, or `?avatar=`/`?agent=`) and drives it with real locomotion; any humanoid rig is retargeted through `src/glb-canonicalize.js` and `src/animation-retarget.js`. |
+| Six live worlds | `ENVIRONMENTS` in [`src/walk-embed.js`](../../src/walk-embed.js) has exactly six entries: `studio`, `void`, `beach`, `sunset`, `night`, `grid`. The live page: "Six built-in environments" and "These are live, not videos." |
+| Picked by a query param | `const ENV_PARAM = (params.get('env') || 'studio')` in [`src/walk-embed.js`](../../src/walk-embed.js); the live page: "set the avatar and world with query params". |
+| No SDK, no build step | Literal on the live page ("No SDK, no build step."), and true of the snippet: a plain iframe with no script include. |
+
+Related docs: [docs/walk-leaderboard.md](../walk-leaderboard.md) (the distance board the page
+teases), and the `walk-sdk/` package README for the scripted companion.
+
+## Media
+
+Captured from the live route with `scripts/capture-doc-media.mjs`. Provenance (route, commit,
+time, sha256) goes in [`public/announce/media-manifest.json`](../../public/announce/media-manifest.json)
+when the recipe is merged into [`data/announce-media.json`](../../data/announce-media.json) and
+`npm run announce:media` runs.
+
+| Shot | File | Notes |
+|---|---|---|
+| `walk-hero` | `/announce/img/walk-hero.webp` | 1600x900 wide viewport, signed out (the page is public). The hero headline beside the live `/walk-embed` iframe with the avatar walking in it. The roaming walk companion is framed out by the capture script's standard site-chrome list, because a second avatar in the corner would confuse which one is the embed. |
+
+**Alt text, required on the post:**
+
+> The three.ws Walk page: a live 3D avatar walking inside a one-tag iframe embed beside the
+> headline Your avatar walks anywhere on the web.
+
+No token tickers or market data appear on this page.
+
+## The post
+
+Pattern: number lead. **147 weighted characters** (per `post-tweet.mjs --dry-run`), inside the
+100-179 band. No tags: nothing about an iframe embed runs on a partner account we could defend.
+
+Postable file: [`walk.post.txt`](./walk.post.txt).
+
+```text
+One iframe tag puts a rigged 3D avatar on any site, walking in one of six live worlds picked by a query param. No SDK, no build step: three.ws/walk
+```
+
+Ship it with `walk-hero` attached and the alt text above.
+
+### Why it is written that way
+
+"Your avatar walks anywhere on the web" is the page headline, and a close variant of it is already
+one of the quotes the page cites from @trythreews (`data/walk-social.json`), so the post does not
+repeat it. The developer's question is cost of adoption, and the
+honest answer is small enough to be the hook: one tag, one query parameter, nothing to install. The
+count of worlds is a number the code pins at six, so it will not drift.
+
+The Chrome extension was cut. The landing pitches it, but its install path points at a docs page
+rather than a store listing, and a post that sends people to install something should link the
+install. The leaderboard was cut too; it is a second surface, and one post links one surface.
+
+## Telegram variant
+
+```text
+Walk is at three.ws/walk: a 3D avatar that walks on any website from one iframe tag.
+
+<iframe src="https://three.ws/walk-embed?env=void&autoplay=true" style="border:0;background:transparent"></iframe>
+
+- Six built-in worlds (studio, void, beach, sunset, night, grid), picked with ?env=.
+- Bring your own avatar with ?avatar= or ?agent=. Any humanoid rig is retargeted, so it walks
+ rather than arriving in a T-pose.
+- WASD or a touch joystick, tap the ground to walk there, and a postMessage API so your page can
+ steer it.
+
+No SDK, no build step. Paste it and it runs.
+
+three.ws/walk
+```
+
+## Changelog
+
+**No new entry.** `/walk` shipped on 2026-06-21 and its `data/pages.json` entry already fed the
+changelog. This pack announces an existing surface and ships nothing new.
+
+## Notes
+
+- **Why /walk is in this batch.** It was the second fallback. `/fits` was skipped as thin (5 settled
+ sales totalling $2.50, the newest 60 days old, 2 fits tracked), `/labor-market` as empty (0 open
+ bounties, 0 settled jobs, `escrow_configured: false` on the live feed), and `/oracle` because its
+ live feed renders third-party launch tickers.
+- **Queue item:** status `review`, lane `developer`, pattern `number`, `notBefore` to be set by the
+ owner. The queue's last item before this batch is also lane `developer` (rig-doctor), so schedule
+ it with another lane in between.
+
+## Posting
+
+Owner-gated, every time. Nothing in this pipeline posts.
+
+```bash
+node scripts/post-tweet.mjs --file docs/announcements/walk.post.txt --dry-run
+```
diff --git a/docs/announcements/walk.post.txt b/docs/announcements/walk.post.txt
new file mode 100644
index 000000000..cbffad4e7
--- /dev/null
+++ b/docs/announcements/walk.post.txt
@@ -0,0 +1 @@
+One iframe tag puts a rigged 3D avatar on any site, walking in one of six live worlds picked by a query param. No SDK, no build step: three.ws/walk