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): tell the community the IBM hosted page and the invitation link are fixed
nirholas033f63bf0c60
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 76134f02d..8e4cc7848 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -15,6 +15,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **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 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 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]`## 2026-09-03diff --git a/data/changelog.json b/data/changelog.jsonindex 47cf0f0cd..974cf5799 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-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.",+ "tags": [+ "fix",+ "infra"+ ],+ "link": "/ibm/hello"+ },{"date": "2026-09-04","title": "Two paid endpoints now quote a price to anyone who asks, instead of an error",@@ -26481,6 +26491,14 @@"feature","improvement"]+ },+ {+ "date": "2026-09-04",+ "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.",+ "tags": [+ "fix"+ ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 111042843..662b2e4d9 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-04T06:40:04.104Z",+ "generated_at": "2026-09-04T07:00:38.198Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -101,6 +101,60 @@"fix"]},+ {+ "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",+ "tags": [+ "fix",+ "infra"+ ]+ },+ {+ "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"+ ]+ },+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "The IRL placements desk can use your location again, and only when you ask it to",+ "summary": "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.",+ "link": null,+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "The Smart Money directory stops asking your browser for pictures it can never get",+ "summary": "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.",+ "link": null,+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "Two paid endpoints now quote a price to anyone who asks, instead of an error",+ "summary": "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.",+ "link": null,+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-04","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex a4f88dd47..95950593e 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -78,6 +78,46 @@<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></item>+ <item>+ <title>The IBM partnership page, hosted on IBM's own site, is live again in every sense</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>+ <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>+ </item>+ <item>+ <title>The invitation link you just created stays on screen</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:The invitation link you just created stays on screen</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item>+ <item>+ <title>The IRL placements desk can use your location again, and only when you ask it to</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:The IRL placements desk can use your location again, and only when you ask it to</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <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 Smart Money directory stops asking your browser for pictures it can never get</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:The Smart Money directory stops asking your browser for pictures it can never get</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item>+ <item>+ <title>Two paid endpoints now quote a price to anyone who asks, instead of an error</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:Two paid endpoints now quote a price to anyone who asks, instead of an error</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item><item><title>When the payment wallets run thin, the money now reaches the right one first</title><link>https://three.ws/changelog</link>