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.

chore(build): regenerate the changelog feed, page index, sitemap and llms manifests

nirholasd2dca7bd19af
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 605db8310..a033ef970 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,11 +6,17 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-09-02
+- **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>.
- **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 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 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-01
diff --git a/data/changelog.json b/data/changelog.json
index da094fb43..bb7ae21ae 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,15 @@
{
"$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": "License terms for three.ws containers on NVIDIA NGC",
+ "summary": "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.",
+ "tags": [
+ "docs"
+ ],
+ "link": "/legal/nvidia-ngc-eula"
+ },
{
"date": "2026-09-02",
"title": "Fixed a footer link that led to a dead page",
@@ -25638,6 +25647,25 @@
"infra"
],
"link": "/agents"
+ },
+ {
+ "date": "2026-09-02",
+ "title": "Every paid endpoint now appears in the public API document",
+ "summary": "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.",
+ "tags": [
+ "improvement",
+ "docs"
+ ]
+ },
+ {
+ "date": "2026-09-02",
+ "title": "Fact checks stop saying \"not enough evidence\" when the evidence was there",
+ "summary": "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.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/fact-checker"
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 122bd97fe..f19871ef1 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,41 @@
{
- "generated_at": "2026-09-02T19:09:33.011Z",
+ "generated_at": "2026-09-02T19:16:34.284Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
"entries": [
+ {
+ "date": "2026-09-02",
+ "type": "launch",
+ "title": "Generated animation seeding",
+ "summary": "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.",
+ "link": "/docs/animation-seeding",
+ "tags": [
+ "launch"
+ ]
+ },
+ {
+ "date": "2026-09-02",
+ "type": "launch",
+ "title": "NVIDIA NGC Container EULA",
+ "summary": "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.",
+ "link": "/legal/nvidia-ngc-eula",
+ "tags": [
+ "launch"
+ ]
+ },
+ {
+ "date": "2026-09-02",
+ "type": "launch",
+ "title": "Print Certificates",
+ "summary": "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>.",
+ "link": "/cert",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-09-02",
"type": "update",
@@ -28,6 +58,17 @@
"infra"
]
},
+ {
+ "date": "2026-09-02",
+ "type": "update",
+ "title": "Every paid endpoint now appears in the public API document",
+ "summary": "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.",
+ "link": null,
+ "tags": [
+ "improvement",
+ "docs"
+ ]
+ },
{
"date": "2026-09-02",
"type": "update",
@@ -51,6 +92,17 @@
"sdk"
]
},
+ {
+ "date": "2026-09-02",
+ "type": "update",
+ "title": "Fact checks stop saying \"not enough evidence\" when the evidence was there",
+ "summary": "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.",
+ "link": "/fact-checker",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-02",
"type": "update",
@@ -61,6 +113,16 @@
"fix"
]
},
+ {
+ "date": "2026-09-02",
+ "type": "update",
+ "title": "License terms for three.ws containers on NVIDIA NGC",
+ "summary": "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.",
+ "link": "/legal/nvidia-ngc-eula",
+ "tags": [
+ "docs"
+ ]
+ },
{
"date": "2026-09-02",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index d08cab121..f3654d0f5 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -6,6 +6,30 @@
<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/>
<description>What's new on three.ws: features, improvements, and releases, newest first.</description>
<language>en</language>
+ <item>
+ <title>Generated animation seeding</title>
+ <link>https://three.ws/docs/animation-seeding</link>
+ <guid isPermaLink="false">2026-09-02:Generated animation seeding</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>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.</description>
+ </item>
+ <item>
+ <title>NVIDIA NGC Container EULA</title>
+ <link>https://three.ws/legal/nvidia-ngc-eula</link>
+ <guid isPermaLink="false">2026-09-02:NVIDIA NGC Container EULA</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>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.</description>
+ </item>
+ <item>
+ <title>Print Certificates</title>
+ <link>https://three.ws/cert</link>
+ <guid isPermaLink="false">2026-09-02:Print Certificates</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <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/&lt;id&gt;.</description>
+ </item>
<item>
<title>Agent profiles start learning about the world again</title>
<link>https://three.ws/agents</link>
@@ -22,6 +46,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 paid endpoint now appears in the public API document</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-09-02:Every paid endpoint now appears in the public API document</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <category>improvement</category>
+ <description>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.</description>
+ </item>
<item>
<title>Every showcased agent now has its own page</title>
<link>https://three.ws/spotlight</link>
@@ -38,6 +70,14 @@
<category>feature</category>
<description>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.</description>
</item>
+ <item>
+ <title>Fact checks stop saying &quot;not enough evidence&quot; when the evidence was there</title>
+ <link>https://three.ws/fact-checker</link>
+ <guid isPermaLink="false">2026-09-02:Fact checks stop saying &quot;not enough evidence&quot; when the evidence was there</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>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 &quot;not enough evidence&quot;, 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.</description>
+ </item>
<item>
<title>Fixed a footer link that led to a dead page</title>
<link>https://three.ws/tty</link>
@@ -46,6 +86,14 @@
<category>fix</category>
<description>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.</description>
</item>
+ <item>
+ <title>License terms for three.ws containers on NVIDIA NGC</title>
+ <link>https://three.ws/legal/nvidia-ngc-eula</link>
+ <guid isPermaLink="false">2026-09-02:License terms for three.ws containers on NVIDIA NGC</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <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 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.json
index 55cfce28e..5a7a74413 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-02T19:09:32.966Z",
+ "generated_at": "2026-09-02T19:16:34.113Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -1271,6 +1271,16 @@
"indexable": true,
"tags": [],
"showcase": false
+ },
+ {
+ "path": "/docs/animation-seeding",
+ "title": "Generated animation seeding",
+ "description": "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.",
+ "added": "2026-09-02",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
}
]
},
@@ -1656,6 +1666,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/cert",
+ "title": "Print Certificates",
+ "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>.",
+ "added": "2026-09-02",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/creations",
"title": "Creator Gallery",
@@ -7571,6 +7591,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/legal/nvidia-ngc-eula",
+ "title": "NVIDIA NGC Container EULA",
+ "description": "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.",
+ "added": "2026-09-02",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/legal/tos",
"title": "Terms of Service",
diff --git a/public/llms-full.txt b/public/llms-full.txt
index eca474a5f..836396afc 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -774,6 +774,12 @@ URL: https://three.ws/stream
A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.
+### Generated animation seeding
+
+URL: https://three.ws/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.
+
## Labs
Experimental features actively shipping. Expect fast iteration.
@@ -1004,6 +1010,12 @@ URL: https://three.ws/minted
Live public gallery of every generated 3D avatar minted as a Metaplex Core NFT through three.ws: interactive viewer, baked provenance, and enforced creator royalties on every card.
+### Print Certificates
+
+URL: https://three.ws/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>.
+
### Creator Gallery
URL: https://three.ws/creations
@@ -4569,6 +4581,12 @@ URL: https://three.ws/legal/eula
License terms for the three.ws Seeker/Saga mobile app: what the license covers, camera and selfie data, updates, and termination.
+### NVIDIA NGC Container EULA
+
+URL: https://three.ws/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.
+
### Terms of Service
URL: https://three.ws/legal/tos
diff --git a/public/llms.txt b/public/llms.txt
index 82b1cedc6..2f8596cf0 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -155,6 +155,7 @@ Create and customize an agent.
- [Skill Bundles](https://three.ws/bundles): Sell several of an agent's skills as one purchase, priced from your own sales instead of a rule of thumb. three.ws finds the buyers who already bought two or more of those skills separately and backtests any price against what they really paid, so you see what the bundle would have earned before you publish it.
- [Terminal renderer](https://three.ws/tty): curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.
- [Progressive Avatars](https://three.ws/stream): A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.
+- [Generated animation seeding](https://three.ws/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.
## Labs
@@ -202,6 +203,7 @@ On-chain features: pay-per-call, token launches, vanity wallets.
- [Agent Launches](https://three.ws/launches): Live public feed of every coin launched by a three.ws agent: market caps, graduation status, and the agent behind each launch.
- [3D Drops](https://three.ws/drops): Launch a supply-capped collection of AI-forged 3D characters. Pick a style, define weighted trait layers, and three.ws rolls the whole supply from a published seed: verifiable rarity, rigged animation-ready art, forged on reveal.
- [Minted 3D Assets](https://three.ws/minted): Live public gallery of every generated 3D avatar minted as a Metaplex Core NFT through three.ws: interactive viewer, baked provenance, and enforced creator royalties on every card.
+- [Print Certificates](https://three.ws/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>.
- [Creator Gallery](https://three.ws/creations): Search, filter, and live-preview the remix bazaar: remix any published 3D creation for a real on-chain USDC royalty, view parent → child lineage, and see the trending assets and top-creator leaderboard. Every model links to its own /m/:id detail page with an interactive viewer, live geometry stats, likes, comments, and suggested models.
- [Live Trading Theater](https://three.ws/theater): Watch agents trade in 3D, in real time. Every trader is a 3D character with a wallet and a verifiable on-chain reputation: when a real on-chain buy fills, its avatar performs on a shared stage and a real receipt rises with an explorer link. Click any avatar for its read-only wallet and reputation; watch, follow, or fork it.
- [Money Pulse](https://three.ws/pulse): The Money Pulse: a real-time, platform-wide feed of three.ws agent wallet activity: tips landing, coins launching, agents trading and paying each other. Every beat is a real on-chain event.
@@ -804,6 +806,7 @@ Long-form announcements, launches, and writing from three.ws.
- [Legal](https://three.ws/legal): Every three.ws policy in one place, plus which address to use to report copyright, abuse, or privacy issues.
- [Privacy Policy](https://three.ws/legal/privacy): What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.
- [End-User License Agreement](https://three.ws/legal/eula): License terms for the three.ws Seeker/Saga mobile app: what the license covers, camera and selfie data, updates, and termination.
+- [NVIDIA NGC Container EULA](https://three.ws/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.
- [Terms of Service](https://three.ws/legal/tos): The agreement between you and three.ws: your account, acceptable use, payments and on-chain activity, liability, and DMCA takedowns.
- [Risk Disclosure](https://three.ws/legal/risk): Risk disclosure for real-funds features: experimental software, total-loss risk, autonomous agents, no liability.
- [Content Policy](https://three.ws/legal/content-policy): What you may publish, mint, and monetise on three.ws: prohibited content, agent behaviour, marketplace listings, and how we enforce.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index 0f79744b1..7018edf9a 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -83,7 +83,7 @@
<main class="sm-wrap">
<div class="sm-hero">
<h1>Sitemap</h1>
- <p>All 880 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
+ <p>All 883 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
<div class="sm-formats">
<a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>
<a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>
@@ -95,7 +95,7 @@
</div>
<div class="sm-filter">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>
- <input id="sm-filter-input" type="search" placeholder="Filter 880 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 883 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
<kbd aria-hidden="true">/</kbd>
</div>
<p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>
@@ -103,6 +103,30 @@
<h2 id="sm-new-title">Newest<a class="sm-new-more" href="/changelog">full changelog &rarr;</a></h2>
<p class="sm-section-desc">The 9 most recently launched pages, straight to the live surface.</p>
<ul class="sm-list">
+ <li>
+ <a href="/docs/animation-seeding">
+ <span class="sm-new-date">Sep 2, 2026</span>
+ <span class="sm-title">Generated animation seeding</span>
+ <span class="sm-path">/docs/animation-seeding</span>
+ <span class="sm-desc">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.</span>
+ </a>
+ </li>
+ <li>
+ <a href="/cert">
+ <span class="sm-new-date">Sep 2, 2026</span>
+ <span class="sm-title">Print Certificates</span>
+ <span class="sm-path">/cert</span>
+ <span class="sm-desc">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/&lt;id&gt;.</span>
+ </a>
+ </li>
+ <li>
+ <a href="/legal/nvidia-ngc-eula">
+ <span class="sm-new-date">Sep 2, 2026</span>
+ <span class="sm-title">NVIDIA NGC Container EULA</span>
+ <span class="sm-path">/legal/nvidia-ngc-eula</span>
+ <span class="sm-desc">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.</span>
+ </a>
+ </li>
<li>
<a href="/drops">
<span class="sm-new-date">Sep 1, 2026</span>
@@ -151,30 +175,6 @@
<span class="sm-desc">How to record a Seeker screen recording of the app with no device: why the Trusted Web Activity makes a browser capture at the real panel geometry a genuine capture, and which moments still have to come from an Android emulator.</span>
</a>
</li>
- <li>
- <a href="/docs/native-widgets">
- <span class="sm-new-date">Aug 29, 2026</span>
- <span class="sm-title">Native widgets: your agent on the home screen</span>
- <span class="sm-path">/docs/native-widgets</span>
- <span class="sm-desc">Put your three.ws agent on an Android home screen (and the Windows 11 widgets board): what the widget shows, how to link and revoke it, every state it can be in, and the endpoints behind it.</span>
- </a>
- </li>
- <li>
- <a href="/portal">
- <span class="sm-new-date">Aug 28, 2026</span>
- <span class="sm-title">Portal</span>
- <span class="sm-path">/portal</span>
- <span class="sm-desc">Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what they say, links become doors you step into, images become billboards. Download the world as a GLB or embed it in your own site.</span>
- </a>
- </li>
- <li>
- <a href="/companion">
- <span class="sm-new-date">Aug 28, 2026</span>
- <span class="sm-title">Companion</span>
- <span class="sm-path">/companion</span>
- <span class="sm-desc">A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.</span>
- </a>
- </li>
</ul>
</section>
<nav class="sm-toc" aria-label="Sections">
@@ -593,7 +593,7 @@
<section class="sm-section" id="build">
<header>
- <h2>Build<span class="sm-count" data-count>69</span></h2>
+ <h2>Build<span class="sm-count" data-count>70</span></h2>
<p class="sm-section-desc">Create and customize an agent.</p>
</header>
<ul class="sm-list">
@@ -1080,6 +1080,13 @@
<span class="sm-desc">A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.</span>
</a>
</li>
+ <li>
+ <a href="/docs/animation-seeding">
+ <span class="sm-title">Generated animation seeding</span>
+ <span class="sm-path">/docs/animation-seeding</span>
+ <span class="sm-desc">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.</span>
+ </a>
+ </li>
</ul>
</section>
@@ -1248,7 +1255,7 @@
<section class="sm-section" id="crypto">
<header>
- <h2>Crypto<span class="sm-count" data-count>138</span></h2>
+ <h2>Crypto<span class="sm-count" data-count>139</span></h2>
<p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p>
</header>
<ul class="sm-list">
@@ -1357,6 +1364,13 @@
<span class="sm-desc">Live public gallery of every generated 3D avatar minted as a Metaplex Core NFT through three.ws: interactive viewer, baked provenance, and enforced creator royalties on every card.</span>
</a>
</li>
+ <li>
+ <a href="/cert">
+ <span class="sm-title">Print Certificates</span>
+ <span class="sm-path">/cert</span>
+ <span class="sm-desc">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/&lt;id&gt;.</span>
+ </a>
+ </li>
<li>
<a href="/creations">
<span class="sm-title">Creator Gallery</span>
@@ -5493,7 +5507,7 @@
<section class="sm-section" id="legal">
<header>
- <h2>Legal<span class="sm-count" data-count>6</span></h2>
+ <h2>Legal<span class="sm-count" data-count>7</span></h2>
</header>
<ul class="sm-list">
@@ -5518,6 +5532,13 @@
<span class="sm-desc">License terms for the three.ws Seeker/Saga mobile app: what the license covers, camera and selfie data, updates, and termination.</span>
</a>
</li>
+ <li>
+ <a href="/legal/nvidia-ngc-eula">
+ <span class="sm-title">NVIDIA NGC Container EULA</span>
+ <span class="sm-path">/legal/nvidia-ngc-eula</span>
+ <span class="sm-desc">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.</span>
+ </a>
+ </li>
<li>
<a href="/legal/tos">
<span class="sm-title">Terms of Service</span>
diff --git a/scripts/audit-page-index.mjs b/scripts/audit-page-index.mjs
index f3c614b73..4801206c2 100644
--- a/scripts/audit-page-index.mjs
+++ b/scripts/audit-page-index.mjs
@@ -51,6 +51,7 @@ const IGNORE = new Set([
'/deploy', // post-create deploy step, reached in-flow
'/demos', // internal demo index
'/ui-juice', // noindex kitchen-sink demo of the ui-juice motion library, not a discovery page
+ '/materialize/ops', // noindex internal fulfillment operator console, gated on the operator allowlist
'/x402', // authenticated x402 checkout, not a discovery page
'/billing/keys', // authenticated x402 subscription-key management, reached in-flow from AWS welcome + dashboard
'/cz', // internal alias