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 feed so the last four entries reach readers
nirholas1f0212c15e9d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex b02be5a50..42748f060 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,9 +7,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-09- **Arm your agent stops telling signed-out visitors to create an agent, and shows them the live conviction stream instead**: A full audit of /oracle/arm found that anyone not signed in was shown “Create a 3D agent to arm it”, a dead end for a visitor with no account, and the rest of the page was hidden behind it. Signing in now gets its own state with sign-in and register buttons, and the live “clearing your bar” preview plus the 30-day win-rate readout stay on screen for everyone, because both run on public data. If the agents list itself fails to load, the page now says so with the status it got back and a Try again button, instead of pretending the account is empty. Four more fixes went with it: the arm switch and the two rule toggles can now be operated from the keyboard (they were focusable but did nothing on Enter or Space), coin artwork routes through the site image proxy so icons stop failing on IPFS gateways, the status line no longer flips back to “Disarmed” when the translation catalog lands after the page has rendered, and every form field now has a real label attached to it. (`/oracle/arm`) `[fix, improvement]`+- **Avatars and token art load again on sites that embed three.ws**: Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists. `[fix]`- **Endpoint Shopper fits a phone, and says something useful when a run finds nothing to buy**: A full audit of /shopper, the page where you describe a task, set a budget, and let an agent shop the x402 Bazaar for endpoints that can answer it. Three things were wrong. A run that came back with no plan and no answer, which is what happens when nothing in the Bazaar matches the task or everything that does prices above your ceiling, painted an empty white column and stopped: no explanation, no way forward. That case now says no endpoints matched, quotes the task back, and offers the three things that change the outcome (rewrite the task, raise the budget, browse the Bazaar) plus a button to run again. Second, when the request could not reach us at all, the page showed the browser's own wording for a dropped connection, which names no cause and suggests no fix; it now says the agent service could not be reached and what to do about it. Third, on a phone narrower than 560px the four navigation links were squeezed into a strip about 76px wide and had to be dragged sideways a few pixels at a time to read; they now wrap onto their own full-width row. Alongside those: the results column announces itself to a screen reader while a run is in flight and when it settles, the Task label sits above its box as intended rather than beside it, and an internal ticket number that had been sitting in the page's headline label since launch is gone. (`/shopper`) `[fix, improvement]`- **Ethereum wallets load on the portfolio page again, keylessly, and every token logo shows up**: A full audit of /portfolio, where you paste any Solana or Ethereum address and get a live portfolio. The Ethereum half had gone dark: the single provider behind it ran out of monthly capacity, so every 0x address answered "Data source unavailable" with nothing behind it. Ethereum now has the same keyless floor Solana has always had. The ETH balance comes from the public Ethereum nodes the rest of the platform already uses, the token list with its prices and icons comes from a public block explorer, and the 24h move comes from the same market source the Solana side uses, with the coverage it achieved stated on the card. The Data panel names whichever lane actually answered, so you can see whether you are reading the paid provider or the free one. Token logos were another visible break: the page pointed your browser straight at an IPFS gateway, which the browser refuses on cross-origin grounds, so every holding fell back to a three-letter monogram and your address bar handed your IP to the gateway on every load. Logos now come through three.ws, sized for the row. Keyboard users could tab onto a slice of the allocation donut and get nothing: the tooltip was wired to an event handler property that browsers do not actually support, so it never fired once; the slice now names its asset and share, and Escape dismisses it. When a lookup fails, the page now shows the reason the server actually sent instead of a generic sentence, and clicking Retry after a rejected address no longer silently reloads the wallet you looked at before it. Underneath, the fallback that names Solana tokens when the primary metadata source is out of quota had never run at all, because of a missing import; token symbols and names come back on that path. (`/portfolio`) `[fix, improvement]`- **Oracle: a failed request now says so, instead of claiming no coins have been scored**: A full audit of /oracle, the fused conviction board for pump.fun launches. When a panel's request failed, the page told you the opposite of the truth: the live feed claimed "Oracle is warming up" and said the engine ships with its backend, the movers, proof, agent-ranking, activity and 3D-graph panels each claimed there was simply nothing to show, and the performance record said the edge was still proving itself. Every one of those is now a real error state that names what went wrong (offline, rate limited, or an engine error) and offers a retry that actually recovers. The Proof gallery had a second bug behind that one: opening it for the first time while the request failed painted nothing at all, not even a skeleton. Searching a symbol Oracle has not scored used to make the results dropdown vanish with no explanation, which reads as a broken search box; it now says there is no match, and says so differently when search itself is down. The conviction-breadth bar's tier segments and legend chips were 10 and 15 pixels tall, too small to reliably tap on a phone, and now carry a full 24-pixel target without changing how the bar looks. Screen readers can finally move from a tab into the panel it opens, every button declares its type, and if a browser is holding a cached copy of an older release the 3D graph explains that and offers a reload instead of retrying a module that can never load. (`/oracle`) `[fix, improvement]`+- **Paid 3D services now refuse a job they cannot deliver, instead of charging for it**: The paid three.ws forge services sold to other AI agents charge the moment the generator accepts a job, and the finished model reaches the buyer only after it lands in our delivery storage. When that storage stopped accepting writes, jobs were still being accepted and charged while no model could ever be handed back. Those services now check that delivery storage is writable before they take the job: if it is not, the call is refused, says so, and is not charged. The check is cached and ignores a one-off blip, so a passing wobble never stops the services selling. The free public health page also had a bug where a storage failure replaced the name of the failing subsystem with the storage provider's error code and printed the request's signing details; it now names the subsystem and reports the reason alone. `[fix, security]`- **Pay-per-call is keyboard-drivable, and it now tells you when the wallet lane is down instead of sitting on a spinner**: A full audit of /pay, the page where an agent pays $0.001 USDC on Solana per call to a paid API. Three things were quietly broken. The wallet pill kept reverting to "loading" after it had already shown a real balance: the page fills that pill from a live balance lookup, but the translation pass that runs a moment later put the placeholder back over it, and the same race hit the session ticker and the wallet setup dialog. Those slots are now marked as owned by the page, so a rendered balance stays put. The whole wallet picker was unreachable without a mouse, because each wallet was a clickable box rather than a button; every wallet is now a real button that tab reaches, Enter and Space activate, and a screen reader announces as selected or not. Both dialogs (the first-visit walkthrough and the wallet setup prompt) now take focus when they open, close on Escape, hand focus back to whatever opened them, and stay hidden from screen readers while closed. States are honest now too. When the agent wallet service is unreachable the page used to tell a signed-out visitor to create their first agent, which was never the problem; it now says wallets are unavailable and offers a Retry that re-runs the lookup without a page reload. A failed activity feed used to leave a row of dots ticking forever and now says the feed is unavailable. The page also gained the heading it never had, one high-contrast focus ring across every control, and a copy pass that removed the long dashes from its description and on-page text. (`/pay`) `[fix, improvement]`- **Payment sessions: the MCP config you copy now works, and a failed load tells you what to do**: The Copy MCP config button on /payments handed out a config that could never connect. It baked in a shortened stand-in for your session token instead of the real one (the real token is shown only once, at creation, and is never retrievable afterwards), and it wrote your sign-in cookie in the wrong format. The snippet now points at two environment variables you export yourself, so the file you save never holds a secret, and a note beside it says exactly what each one is. Failures on the page also stopped hiding behind machine jargon: when the service refused a request, the page showed you its internal code, so trying to create a session with an empty balance read as the word insufficient_credits and nothing else. You now get the plain sentence, and when the balance is the problem, a link straight to Add credits. If the list itself cannot load, the four counters at the top no longer shimmer forever as though something were still loading: the page says what failed, leaves your sessions and budgets untouched, and offers a Try again button. Smaller things along the way: the Docs button used to open a page that did not exist, filtering to a status with nothing in it now offers a way back to the full list, the status filters are reachable on a narrow phone instead of being cut off at the edge, and every field in both dialogs is properly labelled for screen readers. (`/payments`) `[fix, improvement]`- **Pump Dashboard: the live feed shows real launches again instead of raw JSON**: A full audit of /pump-dashboard, the pump.fun trading desk. The headline defect was the feed itself: every event streaming in from the realtime socket was labelled UNKNOWN and printed as a wall of raw JSON, because the socket names its event type in a field the page never read. Launches, graduations and trades now render as readable rows with the token name, symbol, mint and size, whale-sized trades are tagged as whales, and the socket's own subscription acknowledgements stop appearing as feed entries. Recent activity loaded on arrival was stamped with the current time, so a graduation from yesterday claimed to have happened seconds ago; each row now carries the time it actually happened. Filtering the feed to a type with nothing in it left an empty panel with no explanation, and now says what is being filtered and offers a way back to everything. The Token Scanner gave no sign it was working during a scan that routinely takes ten seconds, and could hang forever with no result and no error if a Solana provider accepted the request and never answered; it now shows a busy state, times out, and explains a failure with a way to retry. The Quote Engine printed raw machine codes at you (internal_error, no_curve) where a sentence belongs, and the quote service itself answered a rate-limited Solana chain with a generic internal error instead of an honest "try again in a moment". The Watch List fired a request that could only fail unless you had pointed the dashboard at your own PumpKit backend, and now explains the requirement and takes you to the setting. Twenty-one form fields across the desk got the labels screen readers need, the feed's filter row is now a properly labelled group of toggles, and the high-conviction stats no longer clip their labels on a 320 pixel phone. (`/pump-dashboard`) `[fix, improvement]`diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex a47cea02f..3e372ddfa 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-09T05:43:06.259Z",+ "generated_at": "2026-09-09T05:54:28.300Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3621,+ "total": 3623,"complete": false,"full_feed": "/changelog.json","entries": [@@ -20,6 +20,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Avatars and token art load again on sites that embed three.ws",+ "summary": "Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.",+ "link": null,+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -53,6 +63,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Paid 3D services now refuse a job they cannot deliver, instead of charging for it",+ "summary": "The paid three.ws forge services sold to other AI agents charge the moment the generator accepts a job, and the finished model reaches the buyer only after it lands in our delivery storage. When that storage stopped accepting writes, jobs were still being accepted and charged while no model could ever be handed back. Those services now check that delivery storage is writable before they take the job: if it is not, the call is refused, says so, and is not charged. The check is cached and ignores a one-off blip, so a passing wobble never stops the services selling. The free public health page also had a bug where a storage failure replaced the name of the failing subsystem with the storage provider's error code and printed the request's signing details; it now names the subsystem and reports the reason alone.",+ "link": null,+ "tags": [+ "fix",+ "security"+ ]+ },{"date": "2026-09-09","type": "update",@@ -1599,26 +1620,6 @@"fix","improvement"]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The IBM partnership demos arm wherever the page is opened",- "summary": "The live demo pages loaded their own payment script across the network by full address, so on any address other than the main site (a preview, a local run, a copy published on a partner domain) the browser refused it and the paid demos never armed. Each page now loads the copy it ships with. The publish-once page IBM hosts got the opposite fix: every file it pulls now carries our full address, so its language switcher no longer looks for a file on the host's own domain and comes back empty.",- "link": "/ibm/hello",- "tags": [- "fix"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The invitation link you just created stays on screen",- "summary": "Inviting somebody into your home hands you a link that works once. It used to vanish the instant the household list refreshed behind it, and since we keep only a fingerprint of that link and never the link itself, there was no way to get it back. It now stays put until you close the panel, whether or not the email went out.",- "link": null,- "tags": [- "fix"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 6f26b1048..8d5c9b2ff 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T05:43:06.212Z",+ "generated_at": "2026-09-09T05:54:28.261Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -17,6 +17,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Avatars and token art load again on sites that embed three.ws",+ "summary": "Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.",+ "link": null,+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -50,6 +60,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Paid 3D services now refuse a job they cannot deliver, instead of charging for it",+ "summary": "The paid three.ws forge services sold to other AI agents charge the moment the generator accepts a job, and the finished model reaches the buyer only after it lands in our delivery storage. When that storage stopped accepting writes, jobs were still being accepted and charged while no model could ever be handed back. Those services now check that delivery storage is writable before they take the job: if it is not, the call is refused, says so, and is not charged. The check is cached and ignores a one-off blip, so a passing wobble never stops the services selling. The free public health page also had a bug where a storage failure replaced the name of the failing subsystem with the storage provider's error code and printed the request's signing details; it now names the subsystem and reports the reason alone.",+ "link": null,+ "tags": [+ "fix",+ "security"+ ]+ },{"date": "2026-09-09","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 9e28e2779..bcca8f406 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>fix</category><description>A full audit of /oracle/arm found that anyone not signed in was shown “Create a 3D agent to arm it”, a dead end for a visitor with no account, and the rest of the page was hidden behind it. Signing in now gets its own state with sign-in and register buttons, and the live “clearing your bar” preview plus the 30-day win-rate readout stay on screen for everyone, because both run on public data. If the agents list itself fails to load, the page now says so with the status it got back and a Try again button, instead of pretending the account is empty. Four more fixes went with it: the arm switch and the two rule toggles can now be operated from the keyboard (they were focusable but did nothing on Enter or Space), coin artwork routes through the site image proxy so icons stop failing on IPFS gateways, the status line no longer flips back to “Disarmed” when the translation catalog lands after the page has rendered, and every form field now has a real label attached to it.</description></item>+ <item>+ <title>Avatars and token art load again on sites that embed three.ws</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:Avatars and token art load again on sites that embed three.ws</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.</description>+ </item><item><title>Endpoint Shopper fits a phone, and says something useful when a run finds nothing to buy</title><link>https://three.ws/shopper</link>@@ -38,6 +46,14 @@<category>fix</category><description>A full audit of /oracle, the fused conviction board for pump.fun launches. When a panel's request failed, the page told you the opposite of the truth: the live feed claimed "Oracle is warming up" and said the engine ships with its backend, the movers, proof, agent-ranking, activity and 3D-graph panels each claimed there was simply nothing to show, and the performance record said the edge was still proving itself. Every one of those is now a real error state that names what went wrong (offline, rate limited, or an engine error) and offers a retry that actually recovers. The Proof gallery had a second bug behind that one: opening it for the first time while the request failed painted nothing at all, not even a skeleton. Searching a symbol Oracle has not scored used to make the results dropdown vanish with no explanation, which reads as a broken search box; it now says there is no match, and says so differently when search itself is down. The conviction-breadth bar's tier segments and legend chips were 10 and 15 pixels tall, too small to reliably tap on a phone, and now carry a full 24-pixel target without changing how the bar looks. Screen readers can finally move from a tab into the panel it opens, every button declares its type, and if a browser is holding a cached copy of an older release the 3D graph explains that and offers a reload instead of retrying a module that can never load.</description></item>+ <item>+ <title>Paid 3D services now refuse a job they cannot deliver, instead of charging for it</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:Paid 3D services now refuse a job they cannot deliver, instead of charging for it</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The paid three.ws forge services sold to other AI agents charge the moment the generator accepts a job, and the finished model reaches the buyer only after it lands in our delivery storage. When that storage stopped accepting writes, jobs were still being accepted and charged while no model could ever be handed back. Those services now check that delivery storage is writable before they take the job: if it is not, the call is refused, says so, and is not charged. The check is cached and ignores a one-off blip, so a passing wobble never stops the services selling. The free public health page also had a bug where a storage failure replaced the name of the failing subsystem with the storage provider's error code and printed the request's signing details; it now names the subsystem and reports the reason alone.</description>+ </item><item><title>Pay-per-call is keyboard-drivable, and it now tells you when the wallet lane is down instead of sitting on a spinner</title><link>https://three.ws/pay</link>