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
chore(changelog): regenerate the public changelog feeds and the features manifest
nirholasb65f0ab14f46
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex a033ef970..d38ae5abc 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -9,14 +9,17 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Generated animation seeding** (`/docs/animation-seeding`): How three.ws generates its own animation clips: the text-to-motion GPU lane, the world-space quality gate that judges joint positions instead of raw rotations, the resumable bulk runner, and the rotating free subset.- **NVIDIA NGC Container EULA** (`/legal/nvidia-ngc-eula`): License terms for three.ws container images distributed through the NVIDIA NGC catalog: what the license covers, the model weights the image does not ship, and the data the container does not collect.- **Print Certificates** (`/cert`): Check the certificate of authenticity that ships with every three.ws physical print. Scan the code on the box or type the certificate number to see the original 3D model spinning, its edition number, the SHA-256 of the exact bytes that went to the printer, and the Solana transaction attesting both. Each certificate lives at /cert/<id>.+- **A single page now shows every way an x402 payment can fail, before it stops the economy**: The platform already recorded every rejected, failed and replayed payment, but nothing displayed them, so the first sign of trouble was usually the economy halting. The new payment-outcomes board reads that record live: how many payments settled and how many failed, how many were refused as invalid before settling, how many were replayed copies of an earlier payment, the reasons behind each, and the balance of every wallet that funds a settlement against the floor it stops working at. That last panel matters most during an outage, because a starved fee wallet and a broken payment rail look identical from outside and need opposite fixes. Where a number could not actually be measured the board says so rather than showing a reassuring zero. Operator tooling, behind the same sign-in as the other internal boards. (`/docs/x402-endpoints`) `[feature, infra]`- **Agent profiles start learning about the world again**: Every agent profile reads an index of what that agent has done on-chain, and that index had quietly stopped filling. Each agent is crawled from the last transaction the platform saw for it, and the crawl asks whichever node is not busy; nodes disagree about how far back they keep history, so a bookmark written by one was regularly unreadable by the next. That failed the whole read, the bookmark was only ever saved after a successful read, and so an agent would present the same dead bookmark forever and never index another thing. Two thirds of the directory was stuck that way. The crawl now recognises a bookmark no node can resolve, starts again from the newest activity, and clears the dead value instead of writing it back, and there is a one-command recovery for a backlog that has already built up. The same fault had frozen three secondary chains, one of them for four months, including a case where the node said plainly that it no longer holds those blocks while a second node's unrelated complaint was the only thing the crawl saw; those chains now skip forward to the present and record exactly how much history was lost doing it, so the gap is a number rather than a silence. The sweep was also only reaching a fifth of the directory per run, leaving three quarters of its time unused, which put the slowest profiles more than two hours behind; it now covers the whole directory in about seventy minutes. Finally, the platform status page had been calling the whole index down because of a secondary chain nobody reads on a profile, which buried the real fault for weeks: a secondary-chain problem now reports as degraded and says so, and the count of stuck agents is scored in its own right. (`/agents`) `[fix, infra]`- **Agent profiles stopped losing their on-chain history**: Two thirds of the agents in the directory had quietly stopped picking up new on-chain activity. The indexer resumes each agent from the last transaction it saw, and once the RPC provider answering the call no longer held that transaction, the whole read failed and the agent was stuck there permanently: its profile kept loading, it just never learned anything new again. The crawl now notices that its bookmark has gone stale, re-reads from the top and carries on, and the same recovery landed for the secondary chains, where one had been parked on pruned blocks since April. The 1,083 stuck agents have been unstuck. The status page also learned to score this: an index that is erroring rather than lagging used to look perfectly fresh, and a lagging secondary chain no longer reports a platform outage nobody is having. `[fix, infra]`+- **Every 3D service we sell to other agents now publishes its parameters and a working example**: Agents that buy three.ws 3D generation on the OKX.AI marketplace could read what each service does but not how to call it: the listings named no parameters and carried no example request, so a buyer had to guess the argument names. Each listed service now publishes the full set: what it does, every parameter with its type and whether it is required, the request method and tool name, and a copy-pasteable curl command that hits the real endpoint. The parameter list and the example are generated from the same input schema the endpoint enforces, and a test checks each published example against that schema, so an example that the endpoint would reject cannot ship, and renaming an argument updates the listing with it. `[improvement, docs]`- **Every paid endpoint now appears in the public API document**: Agents find three.ws services by reading the machine-readable API document the platform publishes at /openapi.json. That document listed 24 paid endpoints while the platform actually sells 75, because the entries were written by hand and most were never added. The rest answered a perfectly valid payment challenge in production and could still not be found, which is the whole point of publishing the document. Every paid endpoint is now generated from the same single catalog that already writes the platform's other service listings, so all of them appear with their real price, inputs and payment details, and one written once. The 24 richer hand-written entries are untouched. A test now fails the build if a service is ever added to the catalog without reaching the document, so the gap cannot reopen. `[improvement, docs]`- **Every showcased agent now has its own page**: Agent Spotlight entries got somewhere to live. Each one now has its own page with the agent standing in 3D, the full write-up instead of three clamped lines, a facts panel read live off the agent (skills, conversations, on-chain actions, upvotes), share buttons, and a rail of related entries in the same category. Sharing one finally works too: paste a link anywhere and it unfurls with that entry's headline and the agent's own card rather than the generic showcase image. If you submitted an entry, you can now edit or remove it, which you could not do before: an Edit link on your card opens the write-up ready to change, and removing takes two clicks so it cannot happen by accident. Ranking got fairer as well, with a stable order for entries published at the same moment instead of a shuffle between page loads. (`/spotlight`) `[improvement, feature]`- **Examples gains a voice, an AI's eye on 3D, and a filter**: Three more runnable examples and a way to find them. The avatar can now speak a line you type: the free text-to-speech lane synthesizes it and a new speakAudio() method routes the audio through the same analyser the built-in voice uses, so the mouth follows the real waveform instead of miming. A second example calls the look_at_model tool on the public MCP server and shows exactly what an AI assistant sees when it inspects a mesh: four rendered angles plus a plain-language read on the geometry, which is how an agent judges its own output and decides to try again. A third reads the live tool list off that same server, so the page can never advertise a tool that was renamed or dropped. With seventeen examples the page also gets a filter: type to search names, descriptions and tags, or narrow by tag, and the lanes fold away as they empty. A deep link always wins over an active filter. (`/examples`) `[feature, improvement, sdk]`- **Fact checks stop saying "not enough evidence" when the evidence was there**: A fact check reads five sources and asks a language model where each one stands on the claim. When that model answered in a shape the reader could not parse, every source was quietly recorded as saying nothing, the check reported "not enough evidence", and nothing anywhere said the reading had failed. A live check on whether a tomato is a vegetable came back that way while holding the Supreme Court case that settles the question. The reader now copes with the formats models actually use, including the thinking-out-loud preamble and code fences it used to choke on, and it no longer stops at the first square bracket it sees. When a reply genuinely cannot be read, the check now says it was degraded instead of presenting a verdict it did not earn, which also keeps that answer out of the week-long cache and out of the published accuracy score. The same fault had been collapsing the three search angles behind each check down to one. (`/fact-checker`) `[fix, improvement]`- **Fixed a footer link that led to a dead page**: The terminal page's footer offered an Avatars link that pointed at an address the site does not serve, so clicking it returned a 404 instead of the avatar gallery. It now opens the gallery, the same place every other page sends you. On the knock page, a placeholder link that sat empty until the profile finished loading was removed, so people navigating by keyboard or screen reader no longer land on a link with no name and nowhere to go. (`/tty`) `[fix]`- **License terms for three.ws containers on NVIDIA NGC**: three.ws is preparing to publish its image-to-3D inference server in NVIDIA's NGC catalog, so the licence that will cover those container images is now public. It states plainly what you get: Apache-2.0 source, no model weights inside the image (you bring your own, under the upstream licence), and a container that carries no analytics or telemetry and sends nothing back to us. It sits alongside the other policies on the legal page. (`/legal/nvidia-ngc-eula`) `[docs]`+- **The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves**: The free 3D Studio connector grew to eleven tools when look_at_model landed alongside check_job, but a lot of the writing about it had not caught up: the connector page, the press kit, the partner page, the blog summary, the announcement copy, the press release and the store-submission package still said nine or ten, and the social card enumerated only nine tool names. Every one of those now matches a fresh pull from the live server, the social card lists all eleven, and the module headers inside the connector describe the real catalog including which tools spend generation quota. A test now pins the total, so the next tool to land fails the suite instead of quietly re-opening the same drift. The standalone viewer also stopped crediting the AR launch endpoint with a renderer it no longer loads. Two smaller corrections rode along: the pending-generation example now shows the field that tells a client whether the model coming back is a bare mesh or a finished rig, and the three places the platform pins the 3D viewer library are now explained in one comment, so nobody has to guess why an embed and a standalone page load different builds. (`/docs/mcp-studio`) `[docs, fix]`- **The treasury's self-heal plan now only promises SOL it can actually move**: When the payment rail runs short of the SOL it needs to settle, the platform first tries to heal itself: it looks across its own agent wallets for idle funds and pulls them back to the wallet that pays fees. The preview of that plan was counting wallets it could never open. Eight custodial wallets were encrypted under a key retired during the 2026-07 move to Google Cloud, so the preview kept advertising their balance as available while every real run failed on them, and the plan looked the same the next time anyone checked. The preview now opens each wallet's key before listing it, exactly as a real run does, and reports the ones it cannot open separately with the reason. A plan that reads as capital on hand when the capital is unreachable is worse than no plan at all, and it cost two separate investigations. The health check's settlement hint was corrected to match: it no longer says owner funds are needed only once every wallet reports being at its floor, because a sealed wallet never reports that. `[fix, infra]`## 2026-09-01diff --git a/data/changelog.json b/data/changelog.jsonindex a38cf6196..9d406a761 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$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-09-02",+ "title": "A single page now shows every way an x402 payment can fail, before it stops the economy",+ "summary": "The platform already recorded every rejected, failed and replayed payment, but nothing displayed them, so the first sign of trouble was usually the economy halting. The new payment-outcomes board reads that record live: how many payments settled and how many failed, how many were refused as invalid before settling, how many were replayed copies of an earlier payment, the reasons behind each, and the balance of every wallet that funds a settlement against the floor it stops working at. That last panel matters most during an outage, because a starved fee wallet and a broken payment rail look identical from outside and need opposite fixes. Where a number could not actually be measured the board says so rather than showing a reassuring zero. Operator tooling, behind the same sign-in as the other internal boards.",+ "tags": [+ "feature",+ "infra"+ ],+ "link": "/docs/x402-endpoints"+ },{"date": "2026-09-02","title": "The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves",diff --git a/public/changelog.json b/public/changelog.jsonindex f19871ef1..7a7184955 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-02T19:16:34.284Z",+ "generated_at": "2026-09-02T19:23:04.763Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -36,6 +36,17 @@"launch"]},+ {+ "date": "2026-09-02",+ "type": "update",+ "title": "A single page now shows every way an x402 payment can fail, before it stops the economy",+ "summary": "The platform already recorded every rejected, failed and replayed payment, but nothing displayed them, so the first sign of trouble was usually the economy halting. The new payment-outcomes board reads that record live: how many payments settled and how many failed, how many were refused as invalid before settling, how many were replayed copies of an earlier payment, the reasons behind each, and the balance of every wallet that funds a settlement against the floor it stops working at. That last panel matters most during an outage, because a starved fee wallet and a broken payment rail look identical from outside and need opposite fixes. Where a number could not actually be measured the board says so rather than showing a reassuring zero. Operator tooling, behind the same sign-in as the other internal boards.",+ "link": "/docs/x402-endpoints",+ "tags": [+ "feature",+ "infra"+ ]+ },{"date": "2026-09-02","type": "update",@@ -58,6 +69,17 @@"infra"]},+ {+ "date": "2026-09-02",+ "type": "update",+ "title": "Every 3D service we sell to other agents now publishes its parameters and a working example",+ "summary": "Agents that buy three.ws 3D generation on the OKX.AI marketplace could read what each service does but not how to call it: the listings named no parameters and carried no example request, so a buyer had to guess the argument names. Each listed service now publishes the full set: what it does, every parameter with its type and whether it is required, the request method and tool name, and a copy-pasteable curl command that hits the real endpoint. The parameter list and the example are generated from the same input schema the endpoint enforces, and a test checks each published example against that schema, so an example that the endpoint would reject cannot ship, and renaming an argument updates the listing with it.",+ "link": null,+ "tags": [+ "improvement",+ "docs"+ ]+ },{"date": "2026-09-02","type": "update",@@ -123,6 +145,17 @@"docs"]},+ {+ "date": "2026-09-02",+ "type": "update",+ "title": "The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves",+ "summary": "The free 3D Studio connector grew to eleven tools when look_at_model landed alongside check_job, but a lot of the writing about it had not caught up: the connector page, the press kit, the partner page, the blog summary, the announcement copy, the press release and the store-submission package still said nine or ten, and the social card enumerated only nine tool names. Every one of those now matches a fresh pull from the live server, the social card lists all eleven, and the module headers inside the connector describe the real catalog including which tools spend generation quota. A test now pins the total, so the next tool to land fails the suite instead of quietly re-opening the same drift. The standalone viewer also stopped crediting the AR launch endpoint with a renderer it no longer loads. Two smaller corrections rode along: the pending-generation example now shows the field that tells a client whether the model coming back is a bare mesh or a finished rig, and the three places the platform pins the 3D viewer library are now explained in one comment, so nobody has to guess why an embed and a standalone page load different builds.",+ "link": "/docs/mcp-studio",+ "tags": [+ "docs",+ "fix"+ ]+ },{"date": "2026-09-02","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex f3654d0f5..c8018c60c 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -30,6 +30,14 @@<category>launch</category><description>Check the certificate of authenticity that ships with every three.ws physical print. Scan the code on the box or type the certificate number to see the original 3D model spinning, its edition number, the SHA-256 of the exact bytes that went to the printer, and the Solana transaction attesting both. Each certificate lives at /cert/<id>.</description></item>+ <item>+ <title>A single page now shows every way an x402 payment can fail, before it stops the economy</title>+ <link>https://three.ws/docs/x402-endpoints</link>+ <guid isPermaLink="false">2026-09-02:A single page now shows every way an x402 payment can fail, before it stops the economy</guid>+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The platform already recorded every rejected, failed and replayed payment, but nothing displayed them, so the first sign of trouble was usually the economy halting. The new payment-outcomes board reads that record live: how many payments settled and how many failed, how many were refused as invalid before settling, how many were replayed copies of an earlier payment, the reasons behind each, and the balance of every wallet that funds a settlement against the floor it stops working at. That last panel matters most during an outage, because a starved fee wallet and a broken payment rail look identical from outside and need opposite fixes. Where a number could not actually be measured the board says so rather than showing a reassuring zero. Operator tooling, behind the same sign-in as the other internal boards.</description>+ </item><item><title>Agent profiles start learning about the world again</title><link>https://three.ws/agents</link>@@ -46,6 +54,14 @@<category>fix</category><description>Two thirds of the agents in the directory had quietly stopped picking up new on-chain activity. The indexer resumes each agent from the last transaction it saw, and once the RPC provider answering the call no longer held that transaction, the whole read failed and the agent was stuck there permanently: its profile kept loading, it just never learned anything new again. The crawl now notices that its bookmark has gone stale, re-reads from the top and carries on, and the same recovery landed for the secondary chains, where one had been parked on pruned blocks since April. The 1,083 stuck agents have been unstuck. The status page also learned to score this: an index that is erroring rather than lagging used to look perfectly fresh, and a lagging secondary chain no longer reports a platform outage nobody is having.</description></item>+ <item>+ <title>Every 3D service we sell to other agents now publishes its parameters and a working example</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-02:Every 3D service we sell to other agents now publishes its parameters and a working example</guid>+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Agents that buy three.ws 3D generation on the OKX.AI marketplace could read what each service does but not how to call it: the listings named no parameters and carried no example request, so a buyer had to guess the argument names. Each listed service now publishes the full set: what it does, every parameter with its type and whether it is required, the request method and tool name, and a copy-pasteable curl command that hits the real endpoint. The parameter list and the example are generated from the same input schema the endpoint enforces, and a test checks each published example against that schema, so an example that the endpoint would reject cannot ship, and renaming an argument updates the listing with it.</description>+ </item><item><title>Every paid endpoint now appears in the public API document</title><link>https://three.ws/changelog</link>@@ -94,6 +110,14 @@<category>docs</category><description>three.ws is preparing to publish its image-to-3D inference server in NVIDIA's NGC catalog, so the licence that will cover those container images is now public. It states plainly what you get: Apache-2.0 source, no model weights inside the image (you bring your own, under the upstream licence), and a container that carries no analytics or telemetry and sends nothing back to us. It sits alongside the other policies on the legal page.</description></item>+ <item>+ <title>The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves</title>+ <link>https://three.ws/docs/mcp-studio</link>+ <guid isPermaLink="false">2026-09-02:The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves</guid>+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>+ <category>docs</category>+ <description>The free 3D Studio connector grew to eleven tools when look_at_model landed alongside check_job, but a lot of the writing about it had not caught up: the connector page, the press kit, the partner page, the blog summary, the announcement copy, the press release and the store-submission package still said nine or ten, and the social card enumerated only nine tool names. Every one of those now matches a fresh pull from the live server, the social card lists all eleven, and the module headers inside the connector describe the real catalog including which tools spend generation quota. A test now pins the total, so the next tool to land fails the suite instead of quietly re-opening the same drift. The standalone viewer also stopped crediting the AR launch endpoint with a renderer it no longer loads. Two smaller corrections rode along: the pending-generation example now shows the field that tells a client whether the model coming back is a bare mesh or a finished rig, and the three places the platform pins the 3D viewer library are now explained in one comment, so nobody has to guess why an embed and a standalone page load different builds.</description>+ </item><item><title>The treasury's self-heal plan now only promises SOL it can actually move</title><link>https://three.ws/changelog</link>diff --git a/public/features.json b/public/features.jsonindex 5a7a74413..9fa4d5fb6 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-02T19:16:34.113Z",+ "generated_at": "2026-09-02T19:23:04.330Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",