Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(changelog): regenerate the public changelog feeds with the Anthropic SDK base URL and embed readability entries
nirholas266979af0ef1
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 4b3b481f8..bfba35e17 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,7 +10,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Granite Guardian now answers on three.ws, not just in the docs**: The governance check that screens what an agent is asked to do, and vetoes it when the request is a jailbreak, harmful, or fraudulent, runs on IBM Granite Guardian. It was built to call IBM's hosted watsonx.ai service, so on our live site it answered with a not-configured error, and the new agent identity check quietly skipped itself for the same reason. IBM publishes Granite Guardian's weights openly, so we now run the model ourselves on a dedicated GPU as a second lane: watsonx still leads wherever it is set up, and our own copy answers whenever it is not. Every verdict now says which model and which lane produced it. The identity check also compares a new agent against existing ones using the site's regular embedding service when Granite embeddings are unavailable; it lists the look-alikes it finds but only scores them on Granite, because that is what its thresholds were tuned on. (`/docs/ibm`) `[fix, infra]`- **Paid endpoints now describe themselves the way marketplaces expect**: When an agent or a marketplace asks one of our paid endpoints what it costs, the answer also explains how to call it and what comes back. Around sixty endpoints were sending that explanation in an older layout, or in one that did not match its own rules, which is enough for a marketplace to skip the listing without saying why. Every paid endpoint now sends it in the current standard layout, checked against its own rules. We also added a tool that tests our endpoints with the same checklist a marketplace validator uses, so a listing problem shows up on our side first. (`/docs/x402-dev-tools`) `[improvement, fix]`- **Paid x402 endpoints are answering again**: For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us. (`/docs/x402`) `[fix, infra]`+- **Standard Anthropic SDK clients can now use a three.ws agent's AI budget**: The AI proxy behind every embedded three.ws agent now answers at the address an Anthropic SDK or command-line tool builds for itself. Point a client at /api/llm/anthropic/agents/<your agent id> with one of your API keys and it runs on that agent's model, limits, and monthly budget. The proxy also stopped turning such clients away over their defaults: a system prompt sent as a list of text blocks is accepted, and an output limit above 16,000 tokens is lowered to 16,000 instead of rejected. (`/docs/api-reference`) `[feature, sdk]`- **The $THREE page now has a live DEXTools chart and the Social Boost wins**: The $THREE page shows a live candle chart of the three / SOL pair, drawn by DEXTools. Below the platform's own buybacks there is a new section for the community's: the three DEXTools Social Boost prizes $THREE has won so far, $11,382 of buybacks in total, each with a link to its receipt on DEXTools. Social Boost ranks tokens by visits to their DEXTools page, so the section also links straight there. Every visit counts toward the next win. (`/three-token`) `[feature, improvement]`+- **The embedded 3D agent is readable on light websites and quiet in the console**: Two fixes for anyone who has put a three.ws agent on their own site with the two-line embed. The floating widget had no background of its own, so on a light page its white button labels and name vanished into the page; it now has its own dark panel, and the suggestion buttons carry a solid ground, so it reads the same on any site. You can still ask for a transparent or light panel with the background attribute. The embed also made two background requests that browsers blocked on every site but ours, logging errors in the host page's console; those requests now succeed, and only the public, signed-out answer is ever shared across sites. (`/tutorials/embed-in-30-seconds`) `[fix, sdk]`- **The Trade Terminal finally looks the way it was designed**: The Trade Terminal at /trades was written against a set of colors and fonts that the page itself never defined, so browsers quietly fell back to their defaults: Times New Roman text, oversized controls and missing panel colors. The page now defines its own palette, in both dark and light themes, and renders as the dense, monospaced trading terminal it was meant to be. (`/trades`) `[fix]`## 2026-09-17diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 0327e365f..ecdef9044 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-18T09:11:44.939Z",+ "generated_at": "2026-09-18T20:01:50.539Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3707,+ "total": 3709,"complete": false,"full_feed": "/changelog.json","entries": [@@ -53,6 +53,17 @@"infra"]},+ {+ "date": "2026-09-18",+ "type": "update",+ "title": "Standard Anthropic SDK clients can now use a three.ws agent's AI budget",+ "summary": "The AI proxy behind every embedded three.ws agent now answers at the address an Anthropic SDK or command-line tool builds for itself. Point a client at /api/llm/anthropic/agents/<your agent id> with one of your API keys and it runs on that agent's model, limits, and monthly budget. The proxy also stopped turning such clients away over their defaults: a system prompt sent as a list of text blocks is accepted, and an output limit above 16,000 tokens is lowered to 16,000 instead of rejected.",+ "link": "/docs/api-reference",+ "tags": [+ "feature",+ "sdk"+ ]+ },{"date": "2026-09-18","type": "update",@@ -64,6 +75,17 @@"improvement"]},+ {+ "date": "2026-09-18",+ "type": "update",+ "title": "The embedded 3D agent is readable on light websites and quiet in the console",+ "summary": "Two fixes for anyone who has put a three.ws agent on their own site with the two-line embed. The floating widget had no background of its own, so on a light page its white button labels and name vanished into the page; it now has its own dark panel, and the suggestion buttons carry a solid ground, so it reads the same on any site. You can still ask for a transparent or light panel with the background attribute. The embed also made two background requests that browsers blocked on every site but ours, logging errors in the host page's console; those requests now succeed, and only the public, signed-out answer is ever shared across sites.",+ "link": "/tutorials/embed-in-30-seconds",+ "tags": [+ "fix",+ "sdk"+ ]+ },{"date": "2026-09-18","type": "update",@@ -1597,28 +1619,6 @@"fix","improvement"]- },- {- "date": "2026-09-08",- "type": "update",- "title": "Pages stop re-announcing text they had already shown",- "summary": "The translation layer walks the page when its dictionary arrives and writes the right words into every labelled element. On English, which is what the page already shipped, almost every one of those writes put back exactly the text that was there. Browsers do not treat that as nothing: replacing text is a new paint, and the measurement browsers report for how quickly a page shows its main content was being reset to whenever the dictionary happened to land. The home page's headline had painted in 2.3 seconds and was being scored at 10.2. The pass now checks before it writes, so a page that is already correct is left alone.",- "link": "/",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-08",- "type": "update",- "title": "Paying for something no longer depends on our wallet having gas in it",- "summary": "Every Solana payment on three.ws was quietly gasless: we paid the tiny network fee on your behalf so you could pay with USDC or $THREE without owning any SOL. That is a convenience, but it had been wired as a requirement, so when the wallet we pay those fees from ran empty, every paid page stopped accepting money altogether. The club door and its dance tips returned an error for four days, and sixteen other paid endpoints (asset downloads, skill calls, print orders, cosmetic purchases and the rest) were in the same state, all of them sitting on a perfectly good account that was ready to receive. Receiving money never actually needed our wallet to have anything in it. When we cannot cover the fee, the payment now simply asks you to cover it yourself, which is a fraction of a cent and what most wallets do everywhere else, and the checkout tells you before you approve rather than letting your wallet be the first to mention it. Gasless comes back on its own the moment our wallet is topped up. Two related things got clearer: paying in $THREE stays available in that mode instead of disappearing, and if your own wallet is short on SOL the message now says so and tells you to add a little, instead of claiming we were the ones with the problem.",- "link": "/club",- "tags": [- "fix",- "improvement"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 27da1377c..dca4641cb 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-18T09:11:44.888Z",+ "generated_at": "2026-09-18T20:01:50.447Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -50,6 +50,17 @@"infra"]},+ {+ "date": "2026-09-18",+ "type": "update",+ "title": "Standard Anthropic SDK clients can now use a three.ws agent's AI budget",+ "summary": "The AI proxy behind every embedded three.ws agent now answers at the address an Anthropic SDK or command-line tool builds for itself. Point a client at /api/llm/anthropic/agents/<your agent id> with one of your API keys and it runs on that agent's model, limits, and monthly budget. The proxy also stopped turning such clients away over their defaults: a system prompt sent as a list of text blocks is accepted, and an output limit above 16,000 tokens is lowered to 16,000 instead of rejected.",+ "link": "/docs/api-reference",+ "tags": [+ "feature",+ "sdk"+ ]+ },{"date": "2026-09-18","type": "update",@@ -61,6 +72,17 @@"improvement"]},+ {+ "date": "2026-09-18",+ "type": "update",+ "title": "The embedded 3D agent is readable on light websites and quiet in the console",+ "summary": "Two fixes for anyone who has put a three.ws agent on their own site with the two-line embed. The floating widget had no background of its own, so on a light page its white button labels and name vanished into the page; it now has its own dark panel, and the suggestion buttons carry a solid ground, so it reads the same on any site. You can still ask for a transparent or light panel with the background attribute. The embed also made two background requests that browsers blocked on every site but ours, logging errors in the host page's console; those requests now succeed, and only the public, signed-out answer is ever shared across sites.",+ "link": "/tutorials/embed-in-30-seconds",+ "tags": [+ "fix",+ "sdk"+ ]+ },{"date": "2026-09-18","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex bfc75dd6a..4e11d1e59 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -38,6 +38,14 @@<category>fix</category><description>For several hours on September 18, nearly every paid endpoint on three.ws, the x402 discovery document at /.well-known/x402, the payment facilitator and the MCP server answered with a server error instead of a price. A routine update to the library behind wallet sign-in changed what it needs at startup, and our code tripped over it the moment it loaded, before any request could be served. Agents and marketplace validators that probed us saw a broken seller. The sign-in code now supplies what the library expects, returning buyers can sign back in to what they already paid for exactly as before, and the deploy checks now refuse to ship when the tested dependencies differ from the ones the live site will run, which is how this got past us.</description></item>+ <item>+ <title>Standard Anthropic SDK clients can now use a three.ws agent's AI budget</title>+ <link>https://three.ws/docs/api-reference</link>+ <guid isPermaLink="false">2026-09-18:Standard Anthropic SDK clients can now use a three.ws agent's AI budget</guid>+ <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The AI proxy behind every embedded three.ws agent now answers at the address an Anthropic SDK or command-line tool builds for itself. Point a client at /api/llm/anthropic/agents/<your agent id> with one of your API keys and it runs on that agent's model, limits, and monthly budget. The proxy also stopped turning such clients away over their defaults: a system prompt sent as a list of text blocks is accepted, and an output limit above 16,000 tokens is lowered to 16,000 instead of rejected.</description>+ </item><item><title>The $THREE page now has a live DEXTools chart and the Social Boost wins</title><link>https://three.ws/three-token</link>@@ -46,6 +54,14 @@<category>feature</category><description>The $THREE page shows a live candle chart of the three / SOL pair, drawn by DEXTools. Below the platform's own buybacks there is a new section for the community's: the three DEXTools Social Boost prizes $THREE has won so far, $11,382 of buybacks in total, each with a link to its receipt on DEXTools. Social Boost ranks tokens by visits to their DEXTools page, so the section also links straight there. Every visit counts toward the next win.</description></item>+ <item>+ <title>The embedded 3D agent is readable on light websites and quiet in the console</title>+ <link>https://three.ws/tutorials/embed-in-30-seconds</link>+ <guid isPermaLink="false">2026-09-18:The embedded 3D agent is readable on light websites and quiet in the console</guid>+ <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Two fixes for anyone who has put a three.ws agent on their own site with the two-line embed. The floating widget had no background of its own, so on a light page its white button labels and name vanished into the page; it now has its own dark panel, and the suggestion buttons carry a solid ground, so it reads the same on any site. You can still ask for a transparent or light panel with the background attribute. The embed also made two background requests that browsers blocked on every site but ours, logging errors in the host page's console; those requests now succeed, and only the public, signed-out answer is ever shared across sites.</description>+ </item><item><title>The Trade Terminal finally looks the way it was designed</title><link>https://three.ws/trades</link>diff --git a/public/features.json b/public/features.jsonindex bd6fb1e80..0682a0305 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-18T09:11:44.845Z",+ "generated_at": "2026-09-18T20:01:50.366Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",