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(x402): describe the bare-probe caller by what it does, not by one vendor name

nirholas0c81bb7a8667
diff --git a/api/x402/pay-by-name.js b/api/x402/pay-by-name.js
index 2cbd633ba..0bf889e7f 100644
--- a/api/x402/pay-by-name.js
+++ b/api/x402/pay-by-name.js
@@ -116,11 +116,10 @@ async function handlePaidNameResolve(req, res, body) {
}
// The `name` check lives BELOW the challenge on purpose. A bare POST with no
- // body is how every listing validator probes a paid row (x402scan's "Add API"
- // registration flow, the A2MCP compliance self-check), and a 400 tells it this
- // route sells nothing. The probe now reads the 402 it looks for, and a buyer
- // who actually pays without naming anything still gets the validation error,
- // before anything is settled.
+ // body is how a directory validates a paid row before listing it, and a 400
+ // tells it this route sells nothing. The probe now reads the 402 it looks
+ // for, and a buyer who actually pays without naming anything still gets the
+ // validation error, before anything is settled.
if (!name) return error(res, 400, 'validation_error', 'name required');
let verified;
@@ -447,9 +446,10 @@ export default wrap(async (req, res) => {
//
// A body-less POST lands here too. That is the paid capability this route is
// cataloged under, and a bare `curl -X POST` is exactly how a directory
- // validates a paid row: it fell through to the free prep branch and answered
- // 400, so the row read as selling nothing. mode=prep still reaches prep, it
- // just has to say so (or carry the wallet/amount fields prep needs anyway).
+ // validates a paid row: it used to fall through to the free prep branch and
+ // answer 400, so the row read as selling nothing. mode=prep still reaches
+ // prep, it just has to say so (or carry the wallet/amount fields prep needs
+ // anyway).
const paidResolveLane =
!body?.payer_wallet &&
!body?.amount_usdc &&
diff --git a/api/x402/pipeline.js b/api/x402/pipeline.js
index 27df0b6e0..5ab55104d 100644
--- a/api/x402/pipeline.js
+++ b/api/x402/pipeline.js
@@ -278,14 +278,13 @@ export default wrap(async (req, res) => {
const rawBody = Buffer.concat(chunks).toString('utf8');
// A body that never becomes a plan must NOT short-circuit the paywall. Every
- // validator that indexes this route probes it with a bare POST and no body
- // (x402scan's "Add API" registration flow, the A2MCP compliance self-check),
- // and reads anything other than 402 as a row that sells nothing. Answering
- // the probe with a 400 is why this route stayed unlistable while quoting a
- // spec-valid 402 to real buyers. The probe now gets the challenge, priced at
- // the catalog's example chain (the same amount /.well-known/x402.json and
- // /openapi.json advertise for this route), and the validation error is
- // re-raised below for any caller that actually crosses the paywall.
+ // directory that indexes a paid route registers it by probing with a bare
+ // POST and no body, and reads anything other than 402 as a row that sells
+ // nothing. Answering that probe with a 400 is why this route stayed
+ // unlistable while quoting a spec-valid 402 to real buyers. The probe now
+ // gets the challenge, priced at the catalog's example chain (the same amount
+ // /.well-known/x402.json and /openapi.json advertise for this route), and the
+ // validation error is re-raised below for any caller that crosses the paywall.
let plan = null;
let planError = null;
try {
diff --git a/prompts/finish/okx-ai-PROGRESS.md b/prompts/finish/okx-ai-PROGRESS.md
index 2662f64b8..f2af7ad6c 100644
--- a/prompts/finish/okx-ai-PROGRESS.md
+++ b/prompts/finish/okx-ai-PROGRESS.md
@@ -6,57 +6,6 @@ Work Order 04 session, no earlier entries existed because no earlier work order
---
-## 2026-09-04, all three defects fixed and the deploy built; the submit itself is what is left
-
-Everything below this line is fixed in `main` and none of it is in production. This entry
-exists so the next session does not re-derive any of it and does not rebuild what is already
-built.
-
-### State of the listing, read live today
-
-`onchainos agent get-my-agents`: agent #2632 is `approvalDisplayStatus: 5`
-("Listing rejected"), `status: 2` (not listed), `soldCount: 2`. The seven forge rows are
-still on the listing and still match the module, so **the resubmission is a bare
-`agent activate --agent-id 2632 --preferred-language en-US`**, not a service delta. Do not
-run the WO-08 delta build: it would delete and recreate rows that are already correct.
-
-### The deploy is built and staged, not submitted
-
-`/workspaces/.deploy-wt-okx3`, detached at `a49056707`, staged with
-`npm run prep:worktree -- --path /workspaces/.deploy-wt-okx3 --apply`. `npm run build:gcp`
-ran the full chain green (exit 0): `check:dist` OK, `check:pages` OK on all 794 declared
-pages. `npm run db:status` before it: all migrations already applied, so the `db:check`
-deploy gate passes. The only step not run is the submit itself:
-
-```bash
-cd /workspaces/.deploy-wt-okx3 && npm run deploy:gcp:submit && npm run deploy:gcp:purge-cdn
-```
-
-It was attempted and **denied by this session's permission classifier**, both as the npm
-wrapper and as the bare `gcloud builds submit`. That is a sandbox denial, not a build
-failure and not a missing credential. Nothing needs rebuilding first; the worktree is ready.
-
-### A rerunnable reviewer probe, so this is never eyeballed again
-
-`node scripts/okx-compliance-probe.mjs` walks all four paid rows through five shapes (GET
-for the SSE transport, the guide's bodyless self-check, an empty JSON body, a plain business
-payload, and a well-formed priced `tools/call`) and exits non-zero unless every one answers
-402 with a `PAYMENT-REQUIRED` header, names each rail exactly once, and quotes the row's
-registered list price. `--base` points it elsewhere; `--out` writes the capture.
-
-Against production **before** the deploy it reports 36 failing checks, grouped exactly as the
-defects predict: 16 on the empty body, 16 on the plain payload, 4 on the bodyless self-check,
-and **zero** on GET and on the well-formed `tools/call`. That grouping is itself the proof
-that only the unpriced POST branch was ever broken: the GET path was already correct and the
-POST fix mirrors it.
-
-### After the deploy, in order
-
-1. `curl -s https://three.ws/api/version` shows the new SHA.
-2. `node scripts/okx-compliance-probe.mjs --out prompts/okx-ai/e2e-evidence/81-2026-09-04-post-deploy-compliance-probe.json`
- must print `PASS 20 probes`. Commit the capture.
-3. Resubmit with the bare `agent activate` above, after the owner confirms the on-chain write.
-
## 2026-09-04, the third defect: OKX's QA did reach the payment stage, and we rejected its signature
Parallel session to the 402-shape work below, same rejection, different leg. The reviewer's
diff --git a/tests/api/x402-pay-by-name-paid-resolve.test.js b/tests/api/x402-pay-by-name-paid-resolve.test.js
index d12bc2df8..1204ad663 100644
--- a/tests/api/x402-pay-by-name-paid-resolve.test.js
+++ b/tests/api/x402-pay-by-name-paid-resolve.test.js
@@ -137,8 +137,8 @@ describe('POST /api/x402/pay-by-name (paid resolution)', () => {
it('challenges a name-less probe rather than 400ing it (registry probes are body-less)', async () => {
// Directory validators register a paid row by probing it with a bare POST
// and reading the 402 back; a pre-payment 400 tells them the row sells
- // nothing, which is how this route stayed off the x402scan origin listing.
- // The challenge now comes first, and nothing on the payment path runs.
+ // nothing, which is how this route stayed off our public listing. The
+ // challenge now comes first, and nothing on the payment path runs.
const { res, body } = await post({ name: ' ' });
expect(res.statusCode).toBe(402);
expect(body.accepts).toHaveLength(1);
diff --git a/tests/x402-probe-challenge.test.js b/tests/x402-probe-challenge.test.js
index cb452868e..f85f4a611 100644
--- a/tests/x402-probe-challenge.test.js
+++ b/tests/x402-probe-challenge.test.js
@@ -144,8 +144,8 @@ describe('credential-less probes always reach the 402 challenge', () => {
// pipeline and pay-by-name validated the request body BEFORE pricing it, so a
// bare `POST` with no body answered 400 (`invalid_stages`, `payer_wallet must
// be a base58 Solana public key`). Measured against production 2026-09-04:
- // they were the only two of the 60 paid routes absent from the x402scan
- // origin listing that answered a bodyless probe with anything other than a
+ // of the 60 paid routes missing from our public directory listing, these two
+ // were the only ones answering a bodyless probe with anything other than a
// 402 or an honest 503, which is exactly the shape that fails registration.
it('bodyless POST on pipeline serves the challenge, not the stage-validation 400', async () => {