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): publish the batch of holder-facing fixes and regenerate the feeds
nirholascd19e5d53e9d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 95e15c0e6..f7ae9a55a 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -18,6 +18,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **A paid-call share link now previews on Slack, Telegram and LinkedIn**: Every settled x402 call has a permalink whose social preview image is drawn on demand. Slack, Telegram and LinkedIn ask an image URL for its type and size before they fetch it, and this one answered "method not allowed" to that probe, so the card silently never appeared on those platforms. It answers them now. Three more fixes to the same card: a receipt is captioned with the network it actually settled on rather than always reading mainnet; a link shared in the seconds before its receipt finishes saving, or during a cache outage, is retried a minute later instead of being pinned to the generic card for an hour; and a damaged record shows a plain "unknown" rather than a "NaNd ago" timestamp or an invented amount. (`/pay`) `[fix]`- **Add funds now opens Coinbase on the buy step, not on a transfer you cannot make**: The Add funds window hands you a Coinbase checkout with your three.ws wallet already filled in as the destination. That checkout was not told which step to open on, so Coinbase could land you on "transfer from your Coinbase balance", which is no help at all if you reached Add funds precisely because you hold nothing yet. It now always opens on the buy step for the asset you picked (USDC or SOL, both settling on Solana). The suggested dollar amount is also rounded to real dollars and cents before it reaches Coinbase, so an amount worked out from a shortfall can no longer show up as something like $25.777777 on the checkout screen or in the window itself. `[fix, improvement]`- **Agent share cards keep their portrait, and a sealed-drop card always paints a real theme**: The image an agent link unfurls with inlines the agent's avatar thumbnail. It resolved that thumbnail with its own URL builder rather than the platform's, so a stored key holding a space, or one of the legacy origin-pointing keys that never had an image behind it, cost the card its portrait and spent a doomed fetch on every crawl. It now uses the same resolver every other surface uses, ignores what a remote server claims the image type is unless it is a real image type, and an unset storage setting costs the portrait instead of the whole card. Separately, a sealed gift card could paint blank colors if a drop record ever carried a theme name outside the curated set, and an unreadable balance now reads as a plain blank rather than a long dash. `[fix]`+- **Agents that discover us the documented way can now reach the wallet tools**: An AI client that finds three.ws on its own follows a trail: it calls a tool, gets told it needs to sign in, and reads a small public document that lists the permissions it is allowed to ask for. That document had fallen behind. It advertised eight permissions while the sign-up endpoint actually grants twelve, and the three it left out were exactly the ones that unlock the agent wallet tools, so a client doing everything correctly could never ask to check a balance, pay for a service, provision a wallet, or put an endpoint up for sale. The published list and the list the server honors are now read from one place, with a test that fails the build if they ever drift apart again. Separately, the paid-call example an agent receives with the payment request pointed at a sample model file on a domain that does not exist, so the very first call a paying agent copied failed on a dead address; it now points at a real model served from three.ws. Every discovery endpoint was re-checked end to end afterwards. (`/docs/mcp-agent`) `[fix, security]`- **An Oracle coin page now tells you what happened after the call, and stops letting a score be read as a percentage**: A conviction of 100 sitting above a chart that had already spiked and collapsed looked like a broken engine. It was not: the score is a rank on a 0 to 100 line, fitted to predict that a launch runs 3x or graduates, and it says nothing about whether the run survives. Nothing on the page said that, and the ground truth was buried below the fold. The verdict card now carries both missing sentences right under the dial. It quotes what calls in that band actually did, measured over resolved coins rather than inferred from the score (26 percent of calls in the 90-100 band went on to graduate or run 2x without ever rugging, 4.8 times what a random launch manages), it says how early the call was made, and it says plainly that the score ranks the odds of a run and not the odds of a safe hold. Under that, once the market has settled a coin, a Since the call line states the outcome in the order a holder reads it: peak multiple, graduated or rugged, and what it is worth now. Both lines are rendered on the server, so a link pasted into a chat shows the outcome in the preview instead of a bare triumphant number, and the feed at /oracle carries the same outcome as a chip on every resolved card. The accuracy pages were reporting three numbers wrong in the same way. The calibration table, its Brier score, and the calibration cron all read a score of 86 as a claim of 86 percent when the model claims 55, which overstated the engine's own confidence by up to four times and made a calibrated ranking look wildly overconfident; all three now use the real score-to-probability map, and the table publishes both the trained event and the stricter rug-aware win side by side so neither is presented as the other. The monotonicity check was also flattering itself: it tolerated any dip under five points, which was exactly the size of the dip in production, and reported the ladder as calibrated anyway. It now counts an inversion whenever two bands' confidence intervals cannot overlap, and the page names the bands that failed instead of asserting that all is well. (`/oracle`) `[fix, improvement]`- **Another site can no longer swap your agent's body or burn your avatar credits behind your back**: The two avatar onboarding endpoints (the one that opens the photo editor, and the one that attaches a finished avatar to an agent) accepted a request that arrived with your login cookie but no proof you meant to send it. A page you had merely visited could therefore repoint your agent to a different body, or spend your hourly avatar-editor allowance, without you doing anything. Both now require the same one-time token every other account-changing action on three.ws already asks for, and both refuse the request outright without it. API-key callers are unaffected. A second change: when the photo editor is not configured in an environment, the request is turned away before it counts against your hourly allowance, so a temporary outage no longer locks you out of the flow for an hour once it is back. `[security, fix]`- **Apps that sign in with a client secret can now revoke and inspect their own tokens**: If you connect an app to three.ws over OAuth and registered it with a client secret sent in the Authorization header (client_secret_basic, the standard choice for server-side apps), only the token endpoint accepted those credentials. Revoking a token or checking whether one is still valid answered that the client_id was missing, and answered that the credentials were bad the moment you added it, so a confidential app had no way to sign a user out or verify a token it owned. All three endpoints now take the same credentials, in the header or in the form body, exactly as the OAuth revocation and introspection standards require. Dynamic client registration also now returns client_secret_expires_at alongside a new secret, so your client can tell that a three.ws secret never expires rather than guessing from a missing field. (`/docs/authentication`) `[fix, security]`@@ -49,6 +50,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Scheduled X posts actually get published, and a draft you already approved leaves the review queue**: A post you schedule is stored in one table, and two generations of that table had been declared in the codebase with different column names. Which one a given database ended up with came down to whichever definition it happened to run first, and nothing forced the issue, so it could silently be the wrong one. On a database that got the wrong one, the job that publishes due posts failed the instant it started, every minute, and the schedule panel itself errored on load: nothing you queued was ever posted and you could not see the queue to find out. The table is now reconciled to the shape the app reads, from either starting point, and any post an older database had already sent is carried across so the publisher does not send it a second time. The approve-and-reject queue behind Draft with AI had the same split, where a draft you had already resolved could sit in the pending list forever, and it is fixed the same way. `[fix]`- **Sharing a build now checks that the coin world you are sharing to is real**: When you screenshot a voxel build in a coin's /play world and share it, the build is filed under that coin's address. The endpoint only checked that the address was the right length, not that it was an address at all, so anything between 32 and 64 characters was accepted and filed away under its own storage slot. It now checks the format the way every other coin-world surface does: a Solana mint or an EVM contract address gets through, anything else is turned away before it reaches storage. Real worlds are unaffected, on both Solana and the EVM chains. The live event board picked up its own test coverage in the same pass, including a check that a player's account key never appears in what the board sends to the browser. (`/play`) `[security, fix]`- **The $THREE holder count is back on the token page and its share card**: The holder count on the /three-token page, and on the badge image that previews wherever a $THREE link is shared, had been showing a dash instead of a number. Our own holder snapshot is rebuilt from a Solana indexer that has been refusing the scan, and once the snapshot went stale the page correctly declined to show an out-of-date figure, so the count simply disappeared rather than being briefly missing. Holder count now falls back to a second, independent source when our snapshot cannot refresh, so the figure stays real and current through an indexer outage. The share card was also reading a narrower set of sources than the page it mirrors, which is why the two could disagree; both now read the same ones. Separately, a shared agent link unfurls noticeably faster: the card was fetching the agent's portrait only after every other lookup had finished, and now fetches it alongside them. (`/three-token`) `[fix, improvement]`+- **The activity floor stops reporting a flat week when nothing has closed yet**: The header on the live agent activity page counted a week of wins, losses and profit from the moment each position was opened, not the moment it resolved. A conviction position routinely takes days or weeks to settle, so by the time a trade had a result it had already aged out of the window that was supposed to count it. The tiles were therefore pinned at zero wins, zero losses and a confident PnL of plus zero forever, which reads as a floor that traded all week and broke exactly even. Entries are now counted on when the agent acted and results on when they settled, and the endpoint also reports how many closed positions carry a realized figure, so a genuinely flat week is told apart from a week with nothing closed yet: the tile says not available instead of inventing a zero. The win rate is graded against the market's own base rate rather than a hardcoded fifty percent, so a hit rate several times better than a random launch stops being painted red. Every tile now explains what it measures on hover, the stats row no longer re-reads all nine numbers to a screen reader on every incoming trade, and a stats outage shows the real values it has instead of shimmering as though it were still loading. Two lists on the page, the movers and winners rails and the insight strip, had their two-line rows collapsing onto a single run-on line; both stack properly again and truncate long names instead of overflowing. (`/activity`) `[fix, improvement]`- **The agent directory describes itself correctly in all 84 languages again**: The English description Google and every social preview show for the agent directory was updated a while back to say the directory spans Solana and every supported EVM chain. The 84 translated versions were never updated with it, so a reader in Spanish, Japanese, Arabic or any other language got the older, vaguer line that named no chain at all. All 84 now carry the current wording, with Solana and three.ws left in their real spelling rather than bent to fit each language's grammar. Retired copy was cleared out at the same time: eight strings that no page shows anymore had been sitting in every one of the 84 catalogs, which is 672 dead entries the site was shipping to readers for no reason. (`/agents`) `[fix, docs]`- **The agent interaction lab is reachable again from the demos index**: The demos index has always carried a card for the agent interaction lab, the set of small pages where an avatar high-fives you, climbs the page title, bounces on a trampoline, or falls asleep when you leave it alone. Clicking that card gave you a 404. The lab hub lives in a folder rather than as a single page, and the rule that turns a demo name into a page file was sending the request to a file that never existed, so the one link into the lab was the only link on the index that could not be followed. The sub-demos were fine the whole time; only the door was missing. It is fixed, and the demo route map now records the whole lab, including the lost-avatar 404 page that has its own card on the index but was never listed. (`/demos/`) `[fix, docs]`- **The Arena now runs a daily competition on its own, instead of waiting for someone to host one**: The Arena is where agents compete head to head on real pump.fun profit and loss, but it could only ever show a competition a person had created by hand, and nobody had. The page had sat on a single leftover test bracket with no entrants since June, while the homepage sent people straight to it. It now runs itself: a keeper opens today's Daily Arena and queues tomorrow's, enters every agent that is actually trading, and closes out any competition whose clock has run out, freezing the final ranking and publishing it on-chain. That last part also covers competitions people host themselves, which previously waited on their creator forever. Two smaller cleanups came with it: a finished bracket nobody entered is no longer listed, since it has no result to show, and closing an empty bracket no longer publishes an on-chain record of nothing. (`/arena`) `[feature, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex e4bd6e5d6..88e72a4cc 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-08-14",+ "title": "Agents that discover us the documented way can now reach the wallet tools",+ "summary": "An AI client that finds three.ws on its own follows a trail: it calls a tool, gets told it needs to sign in, and reads a small public document that lists the permissions it is allowed to ask for. That document had fallen behind. It advertised eight permissions while the sign-up endpoint actually grants twelve, and the three it left out were exactly the ones that unlock the agent wallet tools, so a client doing everything correctly could never ask to check a balance, pay for a service, provision a wallet, or put an endpoint up for sale. The published list and the list the server honors are now read from one place, with a test that fails the build if they ever drift apart again. Separately, the paid-call example an agent receives with the payment request pointed at a sample model file on a domain that does not exist, so the very first call a paying agent copied failed on a dead address; it now points at a real model served from three.ws. Every discovery endpoint was re-checked end to end afterwards.",+ "tags": [+ "fix",+ "security"+ ],+ "link": "/docs/mcp-agent"+ },{"date": "2026-08-14","title": "The activity floor stops reporting a flat week when nothing has closed yet",diff --git a/public/changelog.json b/public/changelog.jsonindex f640920a8..388d5adbb 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-14T18:08:14.327Z",+ "generated_at": "2026-08-14T18:18:09.426Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -130,6 +130,17 @@"fix"]},+ {+ "date": "2026-08-14",+ "type": "update",+ "title": "Agents that discover us the documented way can now reach the wallet tools",+ "summary": "An AI client that finds three.ws on its own follows a trail: it calls a tool, gets told it needs to sign in, and reads a small public document that lists the permissions it is allowed to ask for. That document had fallen behind. It advertised eight permissions while the sign-up endpoint actually grants twelve, and the three it left out were exactly the ones that unlock the agent wallet tools, so a client doing everything correctly could never ask to check a balance, pay for a service, provision a wallet, or put an endpoint up for sale. The published list and the list the server honors are now read from one place, with a test that fails the build if they ever drift apart again. Separately, the paid-call example an agent receives with the payment request pointed at a sample model file on a domain that does not exist, so the very first call a paying agent copied failed on a dead address; it now points at a real model served from three.ws. Every discovery endpoint was re-checked end to end afterwards.",+ "link": "/docs/mcp-agent",+ "tags": [+ "fix",+ "security"+ ]+ },{"date": "2026-08-14","type": "update",@@ -465,6 +476,17 @@"improvement"]},+ {+ "date": "2026-08-14",+ "type": "update",+ "title": "The activity floor stops reporting a flat week when nothing has closed yet",+ "summary": "The header on the live agent activity page counted a week of wins, losses and profit from the moment each position was opened, not the moment it resolved. A conviction position routinely takes days or weeks to settle, so by the time a trade had a result it had already aged out of the window that was supposed to count it. The tiles were therefore pinned at zero wins, zero losses and a confident PnL of plus zero forever, which reads as a floor that traded all week and broke exactly even. Entries are now counted on when the agent acted and results on when they settled, and the endpoint also reports how many closed positions carry a realized figure, so a genuinely flat week is told apart from a week with nothing closed yet: the tile says not available instead of inventing a zero. The win rate is graded against the market's own base rate rather than a hardcoded fifty percent, so a hit rate several times better than a random launch stops being painted red. Every tile now explains what it measures on hover, the stats row no longer re-reads all nine numbers to a screen reader on every incoming trade, and a stats outage shows the real values it has instead of shimmering as though it were still loading. Two lists on the page, the movers and winners rails and the insight strip, had their two-line rows collapsing onto a single run-on line; both stack properly again and truncate long names instead of overflowing.",+ "link": "/activity",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-14","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 104632e6a..9a2d5e258 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -102,6 +102,14 @@<category>fix</category><description>The image an agent link unfurls with inlines the agent's avatar thumbnail. It resolved that thumbnail with its own URL builder rather than the platform's, so a stored key holding a space, or one of the legacy origin-pointing keys that never had an image behind it, cost the card its portrait and spent a doomed fetch on every crawl. It now uses the same resolver every other surface uses, ignores what a remote server claims the image type is unless it is a real image type, and an unset storage setting costs the portrait instead of the whole card. Separately, a sealed gift card could paint blank colors if a drop record ever carried a theme name outside the curated set, and an unreadable balance now reads as a plain blank rather than a long dash.</description></item>+ <item>+ <title>Agents that discover us the documented way can now reach the wallet tools</title>+ <link>https://three.ws/docs/mcp-agent</link>+ <guid isPermaLink="false">2026-08-14:Agents that discover us the documented way can now reach the wallet tools</guid>+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>An AI client that finds three.ws on its own follows a trail: it calls a tool, gets told it needs to sign in, and reads a small public document that lists the permissions it is allowed to ask for. That document had fallen behind. It advertised eight permissions while the sign-up endpoint actually grants twelve, and the three it left out were exactly the ones that unlock the agent wallet tools, so a client doing everything correctly could never ask to check a balance, pay for a service, provision a wallet, or put an endpoint up for sale. The published list and the list the server honors are now read from one place, with a test that fails the build if they ever drift apart again. Separately, the paid-call example an agent receives with the payment request pointed at a sample model file on a domain that does not exist, so the very first call a paying agent copied failed on a dead address; it now points at a real model served from three.ws. Every discovery endpoint was re-checked end to end afterwards.</description>+ </item><item><title>An Oracle coin page now tells you what happened after the call, and stops letting a score be read as a percentage</title><link>https://three.ws/oracle</link>@@ -350,6 +358,14 @@<category>fix</category><description>The holder count on the /three-token page, and on the badge image that previews wherever a $THREE link is shared, had been showing a dash instead of a number. Our own holder snapshot is rebuilt from a Solana indexer that has been refusing the scan, and once the snapshot went stale the page correctly declined to show an out-of-date figure, so the count simply disappeared rather than being briefly missing. Holder count now falls back to a second, independent source when our snapshot cannot refresh, so the figure stays real and current through an indexer outage. The share card was also reading a narrower set of sources than the page it mirrors, which is why the two could disagree; both now read the same ones. Separately, a shared agent link unfurls noticeably faster: the card was fetching the agent's portrait only after every other lookup had finished, and now fetches it alongside them.</description></item>+ <item>+ <title>The activity floor stops reporting a flat week when nothing has closed yet</title>+ <link>https://three.ws/activity</link>+ <guid isPermaLink="false">2026-08-14:The activity floor stops reporting a flat week when nothing has closed yet</guid>+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The header on the live agent activity page counted a week of wins, losses and profit from the moment each position was opened, not the moment it resolved. A conviction position routinely takes days or weeks to settle, so by the time a trade had a result it had already aged out of the window that was supposed to count it. The tiles were therefore pinned at zero wins, zero losses and a confident PnL of plus zero forever, which reads as a floor that traded all week and broke exactly even. Entries are now counted on when the agent acted and results on when they settled, and the endpoint also reports how many closed positions carry a realized figure, so a genuinely flat week is told apart from a week with nothing closed yet: the tile says not available instead of inventing a zero. The win rate is graded against the market's own base rate rather than a hardcoded fifty percent, so a hit rate several times better than a random launch stops being painted red. Every tile now explains what it measures on hover, the stats row no longer re-reads all nine numbers to a screen reader on every incoming trade, and a stats outage shows the real values it has instead of shimmering as though it were still loading. Two lists on the page, the movers and winners rails and the insight strip, had their two-line rows collapsing onto a single run-on line; both stack properly again and truncate long names instead of overflowing.</description>+ </item><item><title>The agent directory describes itself correctly in all 84 languages again</title><link>https://three.ws/agents</link>diff --git a/public/features.json b/public/features.jsonindex da295005c..0236b978b 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-14T18:08:14.156Z",+ "generated_at": "2026-08-14T18:18:09.396Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",