Skip to content

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.

docs(okx): record what a paid row must answer a bodyless probe, and tell buyers

nirholas5053d0521c2a
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b5081661f..90c40c1a7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-09-04
- **A knock now holds the money until you actually get a reply**: Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run. `[feature, security]`
+- **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]`
## 2026-09-03
diff --git a/data/changelog.json b/data/changelog.json
index a959d87bd..3d1c9fbbb 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,14 @@
{
"$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 3D services we sell to other agents quote one clear price, however they are asked",
+ "summary": "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.",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-04",
"title": "The IBM partnership demos arm wherever the page is opened",
diff --git a/docs/okx-marketplace.md b/docs/okx-marketplace.md
index 008f1da4b..c387a665c 100644
--- a/docs/okx-marketplace.md
+++ b/docs/okx-marketplace.md
@@ -230,7 +230,16 @@ unit tests in [`tests/api/okx-forge.test.js`](../tests/api/okx-forge.test.js).
- **Retried payments are safe.** The same payment plus the same body replays the same
response through the idempotency cache instead of running a second job.
- **Each rail is advertised once**, and every rail in a service's 402 quotes the same
- amount, derived from the catalog module.
+ amount, derived from the catalog module. That holds for *every* unpaid POST, not just a
+ well-formed `tools/call`: a body that names no priced tool (an empty body, a plain
+ business payload, a mistyped tool name) is quoted at the row's list price rather than
+ falling back to the platform default, so a buyer never reads two prices for one rail.
+- **A bare `POST` is answered with the quotation, not a content-type error.** The A2MCP
+ guide's compliance self-check is `curl -i -X POST <endpoint>` with no body and no
+ `content-type`, and its pass condition for a paid row is `HTTP 402` carrying
+ `PAYMENT-REQUIRED`. Every paid row answers it that way. Unparseable bytes from a caller
+ that is already past the paywall get the JSON-RPC parse error (`-32700`), and nothing
+ settles because nothing ran.
> **Not yet demonstrated end to end.** The X Layer rail reports `settleable: true` in
> production, but no *funded* call has settled on-chain against these endpoints yet: the
diff --git a/public/changelog.json b/public/changelog.json
index 7c16b797c..a6b15ed3a 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-04T01:47:50.604Z",
+ "generated_at": "2026-09-04T01:50:19.386Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -17,6 +17,16 @@
"security"
]
},
+ {
+ "date": "2026-09-04",
+ "type": "update",
+ "title": "The 3D services we sell to other agents quote one clear price, however they are asked",
+ "summary": "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.",
+ "link": null,
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-04",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index a0bbdf1ea..e89034ef9 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -14,6 +14,14 @@
<category>feature</category>
<description>Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.</description>
</item>
+ <item>
+ <title>The 3D services we sell to other agents quote one clear price, however they are asked</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-09-04:The 3D services we sell to other agents quote one clear price, however they are asked</guid>
+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <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>
diff --git a/public/features.json b/public/features.json
index e61b39876..0ee5ce831 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-04T01:36:21.241Z",
+ "generated_at": "2026-09-04T01:50:19.365Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",