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): lead the CORS fix with the embed it unblocks, not the page that exposed it
nirholas7fc7a2f0250c
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8e4cc7848..2bebb7f21 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -14,10 +14,12 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Knock somebody's door and get your money back if they never answer**: Paying to reach a stranger has meant paying first and hoping. The money left your wallet the moment the payment cleared, and if the person never replied, that was that. Doors can now take escrowed knocks instead: your payment sits in a vault on Solana that the recipient cannot touch until they actually answer you. If they answer, they are paid. If they decline, you get everything back and are charged nothing, because reading something and passing on it is not a service. And if they simply never respond before the window they set, anyone at all can trigger the refund and every cent comes back to you, so it does not depend on you remembering to chase it. three.ws holds no key that can move that money, and neither does anyone else. Door owners can turn the lane on in their knock settings and choose how long they get to reply, from an hour to a month. (`/docs/knock`) `[feature, security]`- **Run an escrowed door from your own wallet, and see what the chain actually says**: Door settings now carry the escrowed lane: switch it on, choose how long you want to answer within, and open your on-chain door with your own wallet, which is the only thing that can. The panel reads the chain and tells you the truth rather than your intent, so a door you never opened, or one still charging last month's price, says so plainly instead of quietly turning strangers away. Escrowed knocks in your inbox show how long you have and what answering is worth, replying releases the payment, and refusing refunds the sender in full with no fee. Money still in escrow is no longer counted as earned. `[feature, improvement]`- **The 3D services we sell to other agents quote one clear price, however they are asked**: Our four paid 3D generation services on the OKX.AI agent marketplace answer every caller with a price quote before any work happens. Two flaws in that quote are fixed. A request that arrived with no body and no content type was turned away with a formatting complaint instead of a price, and that is exactly how the marketplace's own compatibility check asks, so the check saw four services that looked like they had no payment set up at all. Separately, a request that named no specific tool got a quote listing the same payment network twice at two different prices, one of them wrong. Every unpaid request now receives a single unambiguous quote at the service's listed price, on each payment network it accepts. `[fix]`+- **The agent answering for us on the OKX.AI marketplace now says when it cannot answer**: Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead. `[fix, infra]`+- **The friends panel tells you when it cannot reach the server, instead of saying you have no friends**: When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: "No friends yet", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word "null" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone. (`/play`) `[fix, improvement]`- **The IBM partnership demos arm wherever the page is opened**: 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. (`/ibm/hello`) `[fix]`-- **The IBM partnership page, hosted on IBM's own site, is live again in every sense**: The partnership page is published once onto IBM's domain and then keeps itself current by quietly pulling the latest copy from three.ws. That pull was being refused by the browser, and so were the payment script and the translation script it loads, because three.ws was not telling other sites they were allowed to read them. The hosted page had quietly frozen on the version baked in at publish time: no language switcher, and the pay-per-call demo never armed. All three now answer any site that asks, the live copy carries its script and translation addresses with it instead of asking IBM's server for files only we have, and a new check runs the page from a stranger's domain so this cannot go unnoticed again. (`/ibm/hello`) `[fix, infra]`- **The invitation link you just created stays on screen**: 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. `[fix]`- **The IRL placements desk can use your location again, and only when you ask it to**: The page that pins your agents to real places offers to measure how far away each pin is and to drop a new one where you are standing. None of it could work: the page arrived with the browser location service switched off for it, so every attempt failed on the spot. Location is allowed on that page now. It also no longer reaches for your position the second the page opens: it reads it only when you have already granted permission, and otherwise waits for you to press one of the location buttons. `[fix, improvement]`+- **The one-line x402 script now works on your site, not just on ours**: Our docs tell you to make any element payable by dropping one line onto your page: a script tag pointing at three.ws/x402.js. On your own domain that line never worked. Your browser asked us whether another site was allowed to read the file and we never answered, so the script was refused and the button stayed inert. The same silence broke the runtime translation script and the language catalogs it reads, and it broke the IBM partnership page that IBM hosts on its own domain: that page keeps itself current by pulling the latest copy from us, and instead had quietly frozen on the version baked in the day it was published. All of it answers any site that asks now. The live copy also carries its own script and translation addresses with it, instead of asking your server for files only we have, and a new check loads that page from a stranger's domain so none of this can go unnoticed again. (`/docs/x402-studio`) `[fix, sdk, infra]`- **The Smart Money directory stops asking your browser for pictures it can never get**: Every wallet in the copy-trading Smart Money list carried a portrait link pointing at an outside image host that serves nobody but its own site. Browsers blocked all of them, so the list drew the trader initials it was designed to fall back on while quietly recording a failed request for each row on screen. That unusable link is no longer sent, so the directory looks exactly as it did with none of the wasted traffic behind it. `[fix, improvement]`- **Two paid endpoints now quote a price to anyone who asks, instead of an error**: The 3D asset pipeline and pay-by-name resolution both checked your request for missing fields before they ever mentioned the price, so a caller who simply asked what they cost got a validation error back. Directories that index paid APIs ask exactly that way, with an empty request, and read an error as a service that sells nothing, which is why neither endpoint could be listed anywhere. Both now answer with the payment challenge and the real price first. The pipeline quotes the published example chain when the request names no stages, and anyone who pays and then sends an incomplete request still gets the same clear validation error, with nothing charged. `[fix, improvement]`- **When the payment wallets run thin, the money now reaches the right one first**: three.ws pays its own on-chain fees from a funding wallet that tops up every engine below its floor. It ranked those engines purely by the size of their shortfall, so a top-up went to whichever wallet was missing the most, and the small wallet that pays the fee on every single payment could sit under its cutoff while the rail stayed shut. The payment wallets are now funded first, so a modest top-up restores settlement instead of a large one being required to reach it by accident. Two related repairs land with it: a wallet holding stablecoins but too little native currency to open the account a swap pays out into is now told exactly how much it is short, instead of retrying the same impossible conversion every half hour, and previewing the rebalancer with a dry run no longer executes real swaps. `[fix, infra]`diff --git a/data/changelog.json b/data/changelog.jsonindex 974cf5799..269160fe0 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -3,13 +3,24 @@"entries": [{"date": "2026-09-04",- "title": "The IBM partnership page, hosted on IBM's own site, is live again in every sense",- "summary": "The partnership page is published once onto IBM's domain and then keeps itself current by quietly pulling the latest copy from three.ws. That pull was being refused by the browser, and so were the payment script and the translation script it loads, because three.ws was not telling other sites they were allowed to read them. The hosted page had quietly frozen on the version baked in at publish time: no language switcher, and the pay-per-call demo never armed. All three now answer any site that asks, the live copy carries its script and translation addresses with it instead of asking IBM's server for files only we have, and a new check runs the page from a stranger's domain so this cannot go unnoticed again.",+ "title": "The friends panel tells you when it cannot reach the server, instead of saying you have no friends",+ "summary": "When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: \"No friends yet\", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word \"null\" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone.","tags": ["fix",+ "improvement"+ ],+ "link": "/play"+ },+ {+ "date": "2026-09-04",+ "title": "The one-line x402 script now works on your site, not just on ours",+ "summary": "Our docs tell you to make any element payable by dropping one line onto your page: a script tag pointing at three.ws/x402.js. On your own domain that line never worked. Your browser asked us whether another site was allowed to read the file and we never answered, so the script was refused and the button stayed inert. The same silence broke the runtime translation script and the language catalogs it reads, and it broke the IBM partnership page that IBM hosts on its own domain: that page keeps itself current by pulling the latest copy from us, and instead had quietly frozen on the version baked in the day it was published. All of it answers any site that asks now. The live copy also carries its own script and translation addresses with it, instead of asking your server for files only we have, and a new check loads that page from a stranger's domain so none of this can go unnoticed again.",+ "tags": [+ "fix",+ "sdk","infra"],- "link": "/ibm/hello"+ "link": "/docs/x402-studio"},{"date": "2026-09-04",@@ -26499,6 +26510,15 @@"tags": ["fix"]+ },+ {+ "date": "2026-09-04",+ "title": "The agent answering for us on the OKX.AI marketplace now says when it cannot answer",+ "summary": "Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead.",+ "tags": [+ "fix",+ "infra"+ ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 662b2e4d9..426485027 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-04T07:00:38.198Z",+ "generated_at": "2026-09-04T07:17:23.399Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -94,22 +94,33 @@{"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",+ "title": "The agent answering for us on the OKX.AI marketplace now says when it cannot answer",+ "summary": "Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead.",+ "link": null,"tags": [- "fix"+ "fix",+ "infra"]},{"date": "2026-09-04","type": "update",- "title": "The IBM partnership page, hosted on IBM's own site, is live again in every sense",- "summary": "The partnership page is published once onto IBM's domain and then keeps itself current by quietly pulling the latest copy from three.ws. That pull was being refused by the browser, and so were the payment script and the translation script it loads, because three.ws was not telling other sites they were allowed to read them. The hosted page had quietly frozen on the version baked in at publish time: no language switcher, and the pay-per-call demo never armed. All three now answer any site that asks, the live copy carries its script and translation addresses with it instead of asking IBM's server for files only we have, and a new check runs the page from a stranger's domain so this cannot go unnoticed again.",- "link": "/ibm/hello",+ "title": "The friends panel tells you when it cannot reach the server, instead of saying you have no friends",+ "summary": "When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: \"No friends yet\", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word \"null\" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone.",+ "link": "/play","tags": ["fix",- "infra"+ "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"]},{@@ -133,6 +144,18 @@"improvement"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "The one-line x402 script now works on your site, not just on ours",+ "summary": "Our docs tell you to make any element payable by dropping one line onto your page: a script tag pointing at three.ws/x402.js. On your own domain that line never worked. Your browser asked us whether another site was allowed to read the file and we never answered, so the script was refused and the button stayed inert. The same silence broke the runtime translation script and the language catalogs it reads, and it broke the IBM partnership page that IBM hosts on its own domain: that page keeps itself current by pulling the latest copy from us, and instead had quietly frozen on the version baked in the day it was published. All of it answers any site that asks now. The live copy also carries its own script and translation addresses with it, instead of asking your server for files only we have, and a new check loads that page from a stranger's domain so none of this can go unnoticed again.",+ "link": "/docs/x402-studio",+ "tags": [+ "fix",+ "sdk",+ "infra"+ ]+ },{"date": "2026-09-04","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 95950593e..14ad9435d 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -71,20 +71,28 @@<description>Our four paid 3D generation services on the OKX.AI agent marketplace answer every caller with a price quote before any work happens. Two flaws in that quote are fixed. A request that arrived with no body and no content type was turned away with a formatting complaint instead of a price, and that is exactly how the marketplace's own compatibility check asks, so the check saw four services that looked like they had no payment set up at all. Separately, a request that named no specific tool got a quote listing the same payment network twice at two different prices, one of them wrong. Every unpaid request now receives a single unambiguous quote at the service's listed price, on each payment network it accepts.</description></item><item>- <title>The IBM partnership demos arm wherever the page is opened</title>- <link>https://three.ws/ibm/hello</link>- <guid isPermaLink="false">2026-09-04:The IBM partnership demos arm wherever the page is opened</guid>+ <title>The agent answering for us on the OKX.AI marketplace now says when it cannot answer</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:The agent answering for us on the OKX.AI marketplace now says when it cannot answer</guid><pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate><category>fix</category>- <description>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.</description>+ <description>Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead.</description>+ </item>+ <item>+ <title>The friends panel tells you when it cannot reach the server, instead of saying you have no friends</title>+ <link>https://three.ws/play</link>+ <guid isPermaLink="false">2026-09-04:The friends panel tells you when it cannot reach the server, instead of saying you have no friends</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: "No friends yet", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word "null" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone.</description></item><item>- <title>The IBM partnership page, hosted on IBM's own site, is live again in every sense</title>+ <title>The IBM partnership demos arm wherever the page is opened</title><link>https://three.ws/ibm/hello</link>- <guid isPermaLink="false">2026-09-04:The IBM partnership page, hosted on IBM's own site, is live again in every sense</guid>+ <guid isPermaLink="false">2026-09-04:The IBM partnership demos arm wherever the page is opened</guid><pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate><category>fix</category>- <description>The partnership page is published once onto IBM's domain and then keeps itself current by quietly pulling the latest copy from three.ws. That pull was being refused by the browser, and so were the payment script and the translation script it loads, because three.ws was not telling other sites they were allowed to read them. The hosted page had quietly frozen on the version baked in at publish time: no language switcher, and the pay-per-call demo never armed. All three now answer any site that asks, the live copy carries its script and translation addresses with it instead of asking IBM's server for files only we have, and a new check runs the page from a stranger's domain so this cannot go unnoticed again.</description>+ <description>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.</description></item><item><title>The invitation link you just created stays on screen</title>@@ -102,6 +110,14 @@<category>fix</category><description>The page that pins your agents to real places offers to measure how far away each pin is and to drop a new one where you are standing. None of it could work: the page arrived with the browser location service switched off for it, so every attempt failed on the spot. Location is allowed on that page now. It also no longer reaches for your position the second the page opens: it reads it only when you have already granted permission, and otherwise waits for you to press one of the location buttons.</description></item>+ <item>+ <title>The one-line x402 script now works on your site, not just on ours</title>+ <link>https://three.ws/docs/x402-studio</link>+ <guid isPermaLink="false">2026-09-04:The one-line x402 script now works on your site, not just on ours</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Our docs tell you to make any element payable by dropping one line onto your page: a script tag pointing at three.ws/x402.js. On your own domain that line never worked. Your browser asked us whether another site was allowed to read the file and we never answered, so the script was refused and the button stayed inert. The same silence broke the runtime translation script and the language catalogs it reads, and it broke the IBM partnership page that IBM hosts on its own domain: that page keeps itself current by pulling the latest copy from us, and instead had quietly frozen on the version baked in the day it was published. All of it answers any site that asks now. The live copy also carries its own script and translation addresses with it, instead of asking your server for files only we have, and a new check loads that page from a stranger's domain so none of this can go unnoticed again.</description>+ </item><item><title>The Smart Money directory stops asking your browser for pictures it can never get</title><link>https://three.ws/changelog</link>