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(changelog): log the agent-payment and MCP doc corrections for holders

nirholas6ce3935e6c58
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8a9a9ade6..107f56d3c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,6 +13,8 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Plan checkout: a paid upgrade can only ever settle on real mainnet, and a late payment is no longer stranded**: Paying for a plan creates a quote, you send the funds, then the server checks the chain before it upgrades you. Three things in that path were wrong. The checkout side has always refused test-network quotes in production, because test-network dollars are free from a faucet, but the confirm side still let a caller name the test network itself, and it is the confirm side that decides which chain it looks at and which dollar it accepts. Both ends now read the same setting, so a production upgrade can only ever be settled by real funds on mainnet. Second, an Ethereum-side payment has to wait twelve blocks before it counts, which meant funds sent near the end of a session could land on-chain and then be refused for arriving late, with the money already gone; that lane now honors the same one-hour grace window the Solana lane has, so an on-chain payment is always claimable. Third, confirming an Ethereum payment could reach a Solana quote and mark it expired, and asking to buy a skill from a malformed agent id answered a generic server error instead of telling you what was wrong with the request. (`/pricing`) `[fix, security]`
- **Self-hosting docs no longer hand you a command that wipes your environment**: The deployment guide told self-hosters to set Cloud Run environment variables with `gcloud run services update --set-env-vars`. That flag replaces the service environment wholesale, so following the instruction for a single key silently deletes every other variable the service had. The guide now uses `--update-env-vars` and says plainly why. Four more corrections landed in the same sweep across the deployment, configuration and contributing pages: the Avaturn signup link and the GitHub Discussions links were dead (Discussions are not enabled on the repository, so bug reports and design questions both go to Issues); the in-browser avatar builder was documented as needing its own hosted origin in production when the normal build already serves it same-origin at /avatar-studio; and three counts that had drifted from the code (cron jobs, MCP server packages, contract tests) were replaced with pointers to the files that hold the real numbers. (`/docs/deployment`) `[docs, fix]`
- **The Agent Economy demo works again when you just pick a service, and it fits a phone screen**: On the Agent Economy page, two 3D agents trade with each other for real SOL: Nova buys a market read, an on-chain insight, or a risk score from Oracle. Picking a service and typing nothing in the optional topic box, which is what almost everyone does, sent the request off in a shape the endpoint refused, so the demo answered with a validation error instead of a trade. It now sends the request correctly, and the endpoint accepts an empty topic besides. On a phone the page was worse than broken: the transaction feed and the status line, the entire output of the demo, were cut off the bottom of the screen with no way to scroll to them, and the floating language button sat on top of the footer links. The centre column now scrolls, the feed keeps a readable height, and the footer stays clickable. Three failure states also stopped lying: a payment that could not go through no longer ends on Transaction complete, a request that never reached the server now says so and offers to try again, and unreadable wallet balances now say they are unavailable and offer a retry instead of spinning forever. (`/agent-economy`) `[fix, improvement]`
+- **The agent-payment and MCP docs now show the code that actually ships**: Three developer docs had drifted from the code they document, in ways that cost a reader real time. The Payment Sessions walkthrough, which is the guide for giving an agent a budget instead of a wallet key, quoted five snippets that no longer match the source: the branch that refuses a payment when the budget will not cover it, the host-allowlist check (which has moved into a shared module so the dry-run simulator and the live enforcement can never disagree), the expiry sweep that refunds unspent budget, the dollars-to-atomic-units helper, and a column missing from the table definition. All five now match the shipped code line for line, and the page links the two source files it had not been pointing at. The MCP article listed the Solana vanity grinder at up to $0.50 scaled by the work done; it is a flat $0.05 per successful grind, and its setup example set a wallet variable the package does not read, so anyone copying it would have configured a payout address that was silently ignored. That example now shows only the variable that works, and says plainly that settlement is USDC on Solana mainnet. The IBM Granite forecasting example showed three data points for a tool that requires at least sixty-four, so a copied sample was guaranteed to be rejected; it now says so. (`/docs/aws-builder-center-agent-payment-sessions`) `[docs, fix]`
+- **The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them**: The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out. `[fix, sdk, docs]`
- **The persona builder stops reporting a model outage as if you had been signed out**: The two routes behind the persona builder (the one that turns your interview answers or a sample of your own writing into a structured persona, and the one that replies to you in that persona's voice) used to hand you whatever status code the model provider returned. If a server-side key expired, the provider answered 401 and so did we, which reads to a browser as an expired session on a request where nothing was wrong with your sign-in. Both now report a provider failure as exactly what it is: a server-side fault, with a plain message and no implication that you need to log back in. Separately, when the platform's daily model-spend ceiling is reached, the builder now says so and tells you when it resets, instead of asking you to retry something that could not have succeeded for the rest of the day. Both routes also now record their model usage against your account, so the spend they generate is visible and capped rather than untracked, and the daily extraction budget now holds across every server instance instead of being counted separately on each one. `[fix, improvement]`
- **The plugin marketplace stops hiding a plugin when you page through it**: Browsing plugins a page at a time could show you the same plugin twice and never show another one at all. The catalogue was sorted by install count and publish date, and the built-in plugins were all published in the same instant with zero installs, so that sort left them tied and the database was free to order the tied rows differently on every request. One plugin therefore landed on two consecutive pages and one fell through the gap. The order is now decided all the way down, so paging through the catalogue returns every plugin exactly once. Searching also takes your text literally: typing a percent sign or an underscore used to act as a database wildcard and match rows it should not. Publishing got stricter at the same time, because a plugin manifest is handed to the model as a tool definition by whoever installs it: a tool name now has to be plain letters, digits, underscores, or hyphens, every tool needs a real description, and a manifest has to fit the same 64KB ceiling that importing one by URL already enforced. And pointing the importer at a repository web page instead of the raw manifest file now says exactly that, rather than showing a raw parser error. (`/marketplace`) `[fix, improvement]`
@@ -2245,7 +2247,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Tutorial · Import an avatar by URL** (`/tutorials/import-avatar-url`): Bring any hosted glTF/GLB avatar into three.ws by link: auto-validated, auto-rigged, ready for an agent.
- **Tutorial · Mine a Solana vanity address** (`/tutorials/mine-vanity-address`): Grind a custom-prefix Solana address in the browser, then prove how it was made with the proof-of-grind receipt, gallery, and bounty market.
- **Tutorial · Place your agent in the real world (IRL)** (`/tutorials/place-agent-irl`): Use camera passthrough, a joystick, and tap-to-place to drop your 3D agent into your physical space: and understand how location privacy works.
-- **Tutorial · Turn a selfie into a 3D avatar** (`/tutorials/selfie-to-avatar`): Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk: then put it on an agent.
+- **Tutorial · Turn a selfie into a 3D avatar** (`/tutorials/selfie-to-avatar`): Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.
- **Walk Anywhere on the Web** (`/walk`): Your 3D avatar walks anywhere on the web. Live demos across six environments, a Chrome extension, one-tag embeds, and a global distance leaderboard.
- **Walk Leaderboard** (`/walk-leaderboard`): Global leaderboard for the walking avatar: distance walked, sites visited, and time, ranked daily, weekly, and all-time.
- **"Fresh from the Forge" thumbnails now show your models**: The community strip on the Forge page shows the newest models people make. Half the tiles were rendering as blank dark squares: for models generated without a reference image, the page builds a thumbnail by snapshotting the 3D model itself, but it was doing that on a one-pixel-wide canvas, so the snapshot came out as a solid block. The snapshot now renders at full thumbnail resolution, and a snapshot that comes back empty cleanly falls back to a labeled prompt card instead of an empty tile. Every card in the strip now shows real artwork. (`/forge`) `[fix]`
@@ -2807,7 +2809,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **AR & WebXR: Place Any 3D Agent in Your Real World** (`/features/ar`): Every three.ws avatar and Forge model has a View in AR button. On mobile it anchors the model to real surfaces through your camera. WebXR on Android, Quick Look on iOS: no app, no download.
- **IRL** (`/irl`): Place a 3D avatar in your real environment. Camera AR passthrough, joystick movement, and tap-to-place 3D objects on your floor.
- **Scene Composer** (`/compose`): Real-time 3D scene composer: forge items from text, attach them to your avatar's skeleton bones, arrange and scale freely, then export your creation or save it as an outfit.
-- **Tutorial · View your 3D model in AR** (`/tutorials/view-in-ar`): See any three.ws model in augmented reality and walk around it in your kitchen: straight from the browser, no app to install. iOS Quick Look and Android WebXR.
+- **Tutorial · View your 3D model in AR** (`/tutorials/view-in-ar`): See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene Viewer, and WebXR.
- **3D model categories, every model is now typed as Avatar, Accessory, Item, Scene, Creature, or Vehicle**: All 3D models on the platform now carry a category that describes what they actually are, not just how they were created. Avatar cards in the marketplace show a color-coded type badge (Avatar, Accessory, Item, Scene, Creature, or Vehicle) and a new filter row lets you browse by type. The Forge gallery shows the same badges on showcase cards, and when you finish forging a model you can tag it right in the result bar with a single click. This is the foundation for the upcoming agent equipment system, where your agents will be able to wear accessories, hold items, and inhabit scenes. (`/marketplace`) `[feature, improvement]`
- **All 14 three.ws MCP servers are now live on npm and the official MCP registry**: Every three.ws MCP server is now publicly installable and discoverable. The eight install-and-run servers ship on npm under the @three-ws scope, pull any of them with one command, e.g. npx -y @three-ws/mcp-server (3D + agent tools), @three-ws/three-token-mcp ($THREE price, hold, and burn), @three-ws/pumpfun-mcp, @three-ws/ibm-x402-mcp, @three-ws/avatar-agent, and more. Together with the six hosted remote servers, all 14 are registered in the official Model Context Protocol registry, so any MCP-compatible client, Claude, Cursor, and others, can find them by name. No more dead install links: the documented commands now work. (`/docs/mcp`) `[sdk, feature]`
- **Animation library expands: 100+ clips, FBX and BVH upload**: The platform animation library grows to 100+ retargeted motion clips drawn from Mixamo, Avaturn packs, and MIT-licensed Three.js example models (Soldier, Michelle, Xbot). The agent dashboard's Upload clip dialog now accepts .glb, .fbx, and .bvh files, FBX and BVH are converted to GLB client-side via three.js loaders before upload, so creators can bring mocap data directly from capture tools without a separate conversion step. A full Mixamo catalog download pipeline (scripts/mixamo-all.mjs) is in place to expand the library to 2,000+ clips as soon as credentials are supplied. (`/temporary`) `[feature, improvement]`
@@ -3119,18 +3121,18 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-05-14
-- **Tutorial · Add a greeting & first speech line** (`/tutorials/greeting-and-first-speech`): Make your agent say hello the moment it loads: and have its mouth move with the words.
+- **Tutorial · Add a greeting & first speech line** (`/tutorials/greeting-and-first-speech`): Make your agent say hello the moment it loads, and have its mouth move with the words.
- **Tutorial · Build a paid x402 endpoint your agent calls** (`/tutorials/paid-x402-endpoint`): Stand up an API that other agents pay USDC to call: using the x402 protocol on Base mainnet. Real money, real flow.
- **Tutorial · Connect Anthropic or OpenAI as the brain** (`/tutorials/connect-ai-brain`): Plug your own model provider into the agent loop. Bring your API key, choose your model, control cost and latency.
- **Tutorial · Custom skill with database + auth** (`/tutorials/skill-with-database-auth`): A real production skill: Postgres-backed CRM lookup, signed requests, per-user permissions, rate limits. Not a toy weather demo.
-- **Tutorial · Customize size, position & background** (`/tutorials/customize-appearance`): Tune every visible knob: bubble size, corner placement, background, rotation speed: entirely through data-* attributes.
+- **Tutorial · Customize size, position & background** (`/tutorials/customize-appearance`): Tune every visible knob on the <agent-3d> element: layout mode, corner placement, size, background, camera framing, and the ambient clip.
- **Tutorial · Deploy to Vercel with a custom domain** (`/tutorials/deploy-to-vercel-custom-domain`): Take a forked three.ws and ship it as agent.yourcompany.com: CI, environment variables, custom domain, SSL, the lot.
- **Tutorial · Drive the agent with the JavaScript API** (`/tutorials/js-api-events`): Listen for the ready event, play animations on demand, make the agent speak from anywhere in your app code.
- **Tutorial · Embed in 30 seconds** (`/tutorials/embed-in-30-seconds`): Drop one script tag into any HTML page. Your agent loads, auto-sizes, and starts animating.
- **Tutorial · Expose your agent as an MCP server** (`/tutorials/mcp-server-for-your-agent`): Wrap your agent in the Model Context Protocol so any MCP-compatible client (Claude Desktop, Cursor, etc.) can drive it.
- **Tutorial · Mint an agent token on Pump.fun** (`/tutorials/mint-pumpfun-token`): Launch a Solana token for your agent, bond it to its on-chain identity, and let people speculate on (or hold) a piece of it.
- **Tutorial · Multi-agent coordination** (`/tutorials/multi-agent-coordination`): Two or more agents on the same page that talk to each other: turn-taking, shared memory, delegating subtasks.
-- **Tutorial · Pick & swap an avatar in Studio** (`/tutorials/swap-avatar-in-studio`): Visually browse the avatar gallery, switch bodies with one click, and have the change ripple to every embed without redeploying.
+- **Tutorial · Pick & swap an avatar in Studio** (`/tutorials/swap-avatar-in-studio`): Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.
- **Tutorial · Self-host the agent backend** (`/tutorials/self-host-agent-backend`): Run the full three.ws backend on your own infrastructure: workers, function endpoints, model proxies. No three.ws dependency in production.
- **Tutorial · Share your agent (link, QR, social preview)** (`/tutorials/share-your-agent`): Get a permanent link to your agent, generate a QR for print, and set the Open Graph preview so it looks good in tweets.
- **Tutorial · Trigger the agent from page events** (`/tutorials/trigger-from-page-events`): Make your agent react to clicks, scrolls, form submits, and route changes: turn it into a real co-pilot, not a chat widget.
diff --git a/data/changelog.json b/data/changelog.json
index 55ba0f274..4897118eb 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,26 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-15",
+ "title": "The agent-payment and MCP docs now show the code that actually ships",
+ "summary": "Three developer docs had drifted from the code they document, in ways that cost a reader real time. The Payment Sessions walkthrough, which is the guide for giving an agent a budget instead of a wallet key, quoted five snippets that no longer match the source: the branch that refuses a payment when the budget will not cover it, the host-allowlist check (which has moved into a shared module so the dry-run simulator and the live enforcement can never disagree), the expiry sweep that refunds unspent budget, the dollars-to-atomic-units helper, and a column missing from the table definition. All five now match the shipped code line for line, and the page links the two source files it had not been pointing at. The MCP article listed the Solana vanity grinder at up to $0.50 scaled by the work done; it is a flat $0.05 per successful grind, and its setup example set a wallet variable the package does not read, so anyone copying it would have configured a payout address that was silently ignored. That example now shows only the variable that works, and says plainly that settlement is USDC on Solana mainnet. The IBM Granite forecasting example showed three data points for a tool that requires at least sixty-four, so a copied sample was guaranteed to be rejected; it now says so.",
+ "tags": [
+ "docs",
+ "fix"
+ ],
+ "link": "/docs/aws-builder-center-agent-payment-sessions"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them",
+ "summary": "The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out.",
+ "tags": [
+ "fix",
+ "sdk",
+ "docs"
+ ]
+ },
{
"date": "2026-08-15",
"title": "The Agent Economy demo works again when you just pick a service, and it fits a phone screen",
diff --git a/public/changelog.json b/public/changelog.json
index e84c54587..44faeaeb5 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T05:46:26.707Z",
+ "generated_at": "2026-08-15T06:32:35.965Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -82,6 +82,29 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The agent-payment and MCP docs now show the code that actually ships",
+ "summary": "Three developer docs had drifted from the code they document, in ways that cost a reader real time. The Payment Sessions walkthrough, which is the guide for giving an agent a budget instead of a wallet key, quoted five snippets that no longer match the source: the branch that refuses a payment when the budget will not cover it, the host-allowlist check (which has moved into a shared module so the dry-run simulator and the live enforcement can never disagree), the expiry sweep that refunds unspent budget, the dollars-to-atomic-units helper, and a column missing from the table definition. All five now match the shipped code line for line, and the page links the two source files it had not been pointing at. The MCP article listed the Solana vanity grinder at up to $0.50 scaled by the work done; it is a flat $0.05 per successful grind, and its setup example set a wallet variable the package does not read, so anyone copying it would have configured a payout address that was silently ignored. That example now shows only the variable that works, and says plainly that settlement is USDC on Solana mainnet. The IBM Granite forecasting example showed three data points for a tool that requires at least sixty-four, so a copied sample was guaranteed to be rejected; it now says so.",
+ "link": "/docs/aws-builder-center-agent-payment-sessions",
+ "tags": [
+ "docs",
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them",
+ "summary": "The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out.",
+ "link": null,
+ "tags": [
+ "fix",
+ "sdk",
+ "docs"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -21812,7 +21835,7 @@
"date": "2026-06-21",
"type": "launch",
"title": "Tutorial · Turn a selfie into a 3D avatar",
- "summary": "Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk: then put it on an agent.",
+ "summary": "Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.",
"link": "/tutorials/selfie-to-avatar",
"tags": [
"launch"
@@ -27380,7 +27403,7 @@
"date": "2026-06-13",
"type": "launch",
"title": "Tutorial · View your 3D model in AR",
- "summary": "See any three.ws model in augmented reality and walk around it in your kitchen: straight from the browser, no app to install. iOS Quick Look and Android WebXR.",
+ "summary": "See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene Viewer, and WebXR.",
"link": "/tutorials/view-in-ar",
"tags": [
"launch"
@@ -29718,7 +29741,7 @@
"date": "2026-05-14",
"type": "launch",
"title": "Tutorial · Add a greeting & first speech line",
- "summary": "Make your agent say hello the moment it loads: and have its mouth move with the words.",
+ "summary": "Make your agent say hello the moment it loads, and have its mouth move with the words.",
"link": "/tutorials/greeting-and-first-speech",
"tags": [
"launch"
@@ -29758,7 +29781,7 @@
"date": "2026-05-14",
"type": "launch",
"title": "Tutorial · Customize size, position & background",
- "summary": "Tune every visible knob: bubble size, corner placement, background, rotation speed: entirely through data-* attributes.",
+ "summary": "Tune every visible knob on the <agent-3d> element: layout mode, corner placement, size, background, camera framing, and the ambient clip.",
"link": "/tutorials/customize-appearance",
"tags": [
"launch"
@@ -29828,7 +29851,7 @@
"date": "2026-05-14",
"type": "launch",
"title": "Tutorial · Pick & swap an avatar in Studio",
- "summary": "Visually browse the avatar gallery, switch bodies with one click, and have the change ripple to every embed without redeploying.",
+ "summary": "Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.",
"link": "/tutorials/swap-avatar-in-studio",
"tags": [
"launch"
diff --git a/public/changelog.xml b/public/changelog.xml
index 822d53650..ddd1fcf27 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -62,6 +62,22 @@
<category>fix</category>
<description>On the Agent Economy page, two 3D agents trade with each other for real SOL: Nova buys a market read, an on-chain insight, or a risk score from Oracle. Picking a service and typing nothing in the optional topic box, which is what almost everyone does, sent the request off in a shape the endpoint refused, so the demo answered with a validation error instead of a trade. It now sends the request correctly, and the endpoint accepts an empty topic besides. On a phone the page was worse than broken: the transaction feed and the status line, the entire output of the demo, were cut off the bottom of the screen with no way to scroll to them, and the floating language button sat on top of the footer links. The centre column now scrolls, the feed keeps a readable height, and the footer stays clickable. Three failure states also stopped lying: a payment that could not go through no longer ends on Transaction complete, a request that never reached the server now says so and offers to try again, and unreadable wallet balances now say they are unavailable and offer a retry instead of spinning forever.</description>
</item>
+ <item>
+ <title>The agent-payment and MCP docs now show the code that actually ships</title>
+ <link>https://three.ws/docs/aws-builder-center-agent-payment-sessions</link>
+ <guid isPermaLink="false">2026-08-15:The agent-payment and MCP docs now show the code that actually ships</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>docs</category>
+ <description>Three developer docs had drifted from the code they document, in ways that cost a reader real time. The Payment Sessions walkthrough, which is the guide for giving an agent a budget instead of a wallet key, quoted five snippets that no longer match the source: the branch that refuses a payment when the budget will not cover it, the host-allowlist check (which has moved into a shared module so the dry-run simulator and the live enforcement can never disagree), the expiry sweep that refunds unspent budget, the dollars-to-atomic-units helper, and a column missing from the table definition. All five now match the shipped code line for line, and the page links the two source files it had not been pointing at. The MCP article listed the Solana vanity grinder at up to $0.50 scaled by the work done; it is a flat $0.05 per successful grind, and its setup example set a wallet variable the package does not read, so anyone copying it would have configured a payout address that was silently ignored. That example now shows only the variable that works, and says plainly that settlement is USDC on Solana mainnet. The IBM Granite forecasting example showed three data points for a tool that requires at least sixty-four, so a copied sample was guaranteed to be rejected; it now says so.</description>
+ </item>
+ <item>
+ <title>The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-15:The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out.</description>
+ </item>
<item>
<title>The persona builder stops reporting a model outage as if you had been signed out</title>
<link>https://three.ws/changelog</link>
@@ -16628,7 +16644,7 @@
<guid isPermaLink="false">2026-06-21:Tutorial · Turn a selfie into a 3D avatar</guid>
<pubDate>Sun, 21 Jun 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk: then put it on an agent.</description>
+ <description>Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.</description>
</item>
<item>
<title>Walk Anywhere on the Web</title>
@@ -20932,7 +20948,7 @@
<guid isPermaLink="false">2026-06-13:Tutorial · View your 3D model in AR</guid>
<pubDate>Sat, 13 Jun 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>See any three.ws model in augmented reality and walk around it in your kitchen: straight from the browser, no app to install. iOS Quick Look and Android WebXR.</description>
+ <description>See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene Viewer, and WebXR.</description>
</item>
<item>
<title>3D model categories, every model is now typed as Avatar, Accessory, Item, Scene, Creature, or Vehicle</title>
@@ -22756,7 +22772,7 @@
<guid isPermaLink="false">2026-05-14:Tutorial · Add a greeting &amp; first speech line</guid>
<pubDate>Thu, 14 May 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>Make your agent say hello the moment it loads: and have its mouth move with the words.</description>
+ <description>Make your agent say hello the moment it loads, and have its mouth move with the words.</description>
</item>
<item>
<title>Tutorial · Build a paid x402 endpoint your agent calls</title>
@@ -22788,7 +22804,7 @@
<guid isPermaLink="false">2026-05-14:Tutorial · Customize size, position &amp; background</guid>
<pubDate>Thu, 14 May 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>Tune every visible knob: bubble size, corner placement, background, rotation speed: entirely through data-* attributes.</description>
+ <description>Tune every visible knob on the &lt;agent-3d&gt; element: layout mode, corner placement, size, background, camera framing, and the ambient clip.</description>
</item>
<item>
<title>Tutorial · Deploy to Vercel with a custom domain</title>
@@ -22844,7 +22860,7 @@
<guid isPermaLink="false">2026-05-14:Tutorial · Pick &amp; swap an avatar in Studio</guid>
<pubDate>Thu, 14 May 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>Visually browse the avatar gallery, switch bodies with one click, and have the change ripple to every embed without redeploying.</description>
+ <description>Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.</description>
</item>
<item>
<title>Tutorial · Self-host the agent backend</title>
diff --git a/public/features.json b/public/features.json
index 62199c26c..1cf5ad55a 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T05:46:26.357Z",
+ "generated_at": "2026-08-15T06:32:35.908Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -6080,7 +6080,7 @@
{
"path": "/tutorials/customize-appearance",
"title": "Tutorial · Customize size, position & background",
- "description": "Tune every visible knob: bubble size, corner placement, background, rotation speed: entirely through data-* attributes.",
+ "description": "Tune every visible knob on the <agent-3d> element: layout mode, corner placement, size, background, camera framing, and the ambient clip.",
"added": "2026-05-14",
"auth": null,
"indexable": true,
@@ -6090,7 +6090,7 @@
{
"path": "/tutorials/swap-avatar-in-studio",
"title": "Tutorial · Pick & swap an avatar in Studio",
- "description": "Visually browse the avatar gallery, switch bodies with one click, and have the change ripple to every embed without redeploying.",
+ "description": "Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.",
"added": "2026-05-14",
"auth": null,
"indexable": true,
@@ -6100,7 +6100,7 @@
{
"path": "/tutorials/greeting-and-first-speech",
"title": "Tutorial · Add a greeting & first speech line",
- "description": "Make your agent say hello the moment it loads: and have its mouth move with the words.",
+ "description": "Make your agent say hello the moment it loads, and have its mouth move with the words.",
"added": "2026-05-14",
"auth": null,
"indexable": true,
@@ -6120,7 +6120,7 @@
{
"path": "/tutorials/selfie-to-avatar",
"title": "Tutorial · Turn a selfie into a 3D avatar",
- "description": "Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk: then put it on an agent.",
+ "description": "Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.",
"added": "2026-06-21",
"auth": null,
"indexable": true,
@@ -6130,7 +6130,7 @@
{
"path": "/tutorials/view-in-ar",
"title": "Tutorial · View your 3D model in AR",
- "description": "See any three.ws model in augmented reality and walk around it in your kitchen: straight from the browser, no app to install. iOS Quick Look and Android WebXR.",
+ "description": "See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene Viewer, and WebXR.",
"added": "2026-06-13",
"auth": null,
"indexable": true,