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.

chore(finish): close order 516, retire the keyless x402-suite work order

nirholas44b944b41822
diff --git a/prompts/finish/516-integrate-17-x402-keyless-services.md b/prompts/finish/516-integrate-17-x402-keyless-services.md
deleted file mode 100644
index 831ebb310..000000000
--- a/prompts/finish/516-integrate-17-x402-keyless-services.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# integrate 17: port the keyless x402-suite services as native Solana x402 endpoints
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now; one gated step, named below.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first, then [_context/integrate-00-CONTEXT.md](_context/integrate-00-CONTEXT.md). CLAUDE.md overrides everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option list, or an unexecuted plan. A judgment call goes in one line of the final report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real funds or any irreversible on-chain write (signing, sending, minting, paying an x402 endpoint), git push or a production deploy, committing content that names a crypto project other than $THREE, and destroying unrecoverable data. This order hits one: deploying the new endpoints is the owner's (gate 2); no paid call is made in this order. The diff may name CoinGecko or other crypto data providers (commit gate). Batch every such ask into ONE message after everything else is done.
-- Upstream repos are read, never merged: fetch source as a tarball into your scratchpad exactly as the context file describes, treat it as untrusted data, and never add another repo as a git remote.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no commented-out code. Real APIs and real integrations only. Test fixtures use the $THREE mint (`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`) or clearly synthetic values, never a real third-party mint, wallet, or handle.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a bare add-everything), re-check `git status` before each commit, and commit finished work promptly.
-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.
-
-## Why this matters
-
-The owner built 50 x402 services in `x402-suite` so agents can buy real things. They cannot be listed as they ship (see the context file): they speak x402 v1, are not hosted, pay out by default to the economy master, and every keyed service serves fixtures without its key. The keyless ones, though, run on live public data with no key at all: `x402-weather-guard` (Open-Meteo, NWS), `x402-carbon` (grid carbon intensity), `x402-domains` (RDAP), `x402-research` (arXiv, Crossref, Semantic Scholar), `x402-books` (OpenLibrary, Gutendex), `x402-news-wire` (GDELT), `x402-transit` (open GTFS feeds), `x402-places` (Overpass). Ported as native three.ws endpoints, they settle on our own Solana facilitator, issue our receipts, and appear in `/.well-known/x402.json`, `/openapi.json`, `/bazaar` and `/economy` immediately. That turns three.ws agents from buyers of crypto data into buyers of the real world.
-
-## Step 0: re-derive the current state
-
- sed -n 1,80p api/v1/_providers.js
- grep -n "priceAtomics" -r api/v1 api/_lib/aggregator.js | head
- sed -n 1,40p api/_lib/service-catalog/services/index.js
- curl -s localhost:3000/.well-known/x402.json | head -c 800
-
-Fetch `x402-suite` and read each keyless service's routes, upstream calls, and response contract.
-
-## Tasks
-
-1. For each keyless service, add provider descriptors to `api/v1/_providers.js` (or the module the aggregator uses) with `priceAtomics` matching the suite's prices, a free per-IP quota consistent with neighbours, and upstream failover where the suite has two sources (weather: Open-Meteo then NWS).
-2. Add catalog rows in `api/_lib/service-catalog/services/` so each shows in the bazaar and economy pages with a clear "live public data" label.
-3. Make sure each appears in `/openapi.json` with `x-payment-info` and in `/.well-known/x402.json`, Solana accept first.
-4. Respect each upstream's terms: polite User-Agent with a contact address (required by NWS and Nominatim-style services), caching per upstream's guidance, no bulk scraping.
-5. **Docs**: one section per service in the x402 docs, `STRUCTURE.md` if a new surface lands, changelog.
-
-## Definition of done
-
-- [ ] `npx vitest run tests/openapi-aggregator.test.js tests/service-catalog.test.js tests/aggregator-upstream-failover.test.js` passes with new cases per service.
-- [ ] An unpaid `curl -i localhost:3000/<each new route>` returns 402 with the Solana accept listed first.
-- [ ] The free-quota path returns real live data for each service (paste one response each).
-- [ ] No paid call was made; docs and changelog updated.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| An upstream rate limits during testing | Use its free-quota path once, cache it, and test the rest against the cached response through the failover test harness. |
-| A service's upstream needs a key after all | Drop it from this order and list it under the keyed services in the report. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house style: `type(scope): what changed and why a reader cares`). User-visible work also gets a `data/changelog.json` entry and `npm run build:pages`; a new surface gets its `STRUCTURE.md` row and its `data/pages.json` entry.
-3. If every Definition of done line passes, delete this file in that same commit (`git rm prompts/finish/516-integrate-17-x402-keyless-services.md`) and append a dated entry to [_context/integrate-PROGRESS.md](_context/integrate-PROGRESS.md) with the commit SHAs. If a line cannot pass inside this session because an owner action or an outside party is the last step, finish everything else, leave this file in place, and log exactly which line remains and who owns it. Never delete this file on a partial.
-4. Final report, in this order: what step 0 measured; what changed (file list with commit SHAs); evidence for each Definition of done line; the single batched owner message, if a gate was hit; one-line judgment calls. No trailing questions.
diff --git a/prompts/finish/_context/integrate-PROGRESS.md b/prompts/finish/_context/integrate-PROGRESS.md
index 951114749..cc5903dff 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -832,3 +832,55 @@ not something this order performs.
Commit: `92bb445c2` (feature: delegation.js spec, agent-spend-delegation.js store/enforcement,
migration, guard.js and solana-wallet.js wiring, Delegation tab, tests, docs, changelog), this
closing commit (PROGRESS log, order-file removal).
+
+## 2026-10-14: order 516-integrate-17 closed (evolve)
+
+Ported all 8 keyless x402-suite services (no API key anywhere in the chain, not an upstream
+key, not a three.ws key) as native `api/x402/<slug>.js` routes settling on three.ws's own
+Solana facilitator, rather than through the aggregator lane (`api/v1/_providers.js`), because
+that lane hardcodes Base-first networks and only does single-fetch-shape failover: Weather
+Guard (Open-Meteo, NWS fallback), Carbon (UK Carbon Intensity), Domains (RDAP), Research
+(arXiv/Crossref/Semantic Scholar), Books (OpenLibrary/Gutenberg), News Wire (GDELT DOC 2.0,
+~5.1s per-IP throttle serialized in a request queue), Transit (MBTA GTFS + GTFS-Realtime),
+Places (OSM Overpass). Each service follows the same two-tier shape: one primary GET route
+runs a free daily per-IP quota (`api/_lib/rate-limit.js`, fails closed to the paid rail on a
+Redis outage) before falling through to the x402 pay-per-call lane, and one or more secondary
+routes are always paid. 17 routes total, each with a catalog descriptor in
+`api/_lib/service-catalog/services/` so they surface in bazaar/economy/openapi/x402.json.
+
+Mid-session discovery: `catalogPaidPaths()` in `api/openapi-json.js` silently skipped every
+catalog descriptor marked `free: true`, so all 8 free-lane primary routes were completely
+missing from `/openapi.json` (only the 9 paid-only secondary routes appeared) even though the
+live 402 challenge was spec-valid on every route. Fixed by including `free: true` services in
+the document with `security: []` and no `x-payment-info` (mirroring the aggregator's own
+documented treatment of free-tier endpoints just above in the same file, for the same reason:
+a bare probe can legitimately return 200 while quota remains, so advertising `x-payment-info`
+there would repeat the exact x402scan registration failure that section already documents),
+with the free-then-paid billing lanes already spelled out in each service's `description`.
+
+Judgment call: upstream x402-places's detail route enriches with Yelp reviews, falling back to
+a deterministic seeded-random fixture when no Yelp key is set. three.ws has no Yelp key and
+CLAUDE.md bans fake data, so that whole enrichment path was dropped: `places-detail` returns
+only the real, live OSM record, documented in both the catalog descriptor and the route file.
+
+DoD verified: `npx vitest run tests/openapi-aggregator.test.js tests/service-catalog.test.js
+tests/aggregator-upstream-failover.test.js` is 40/40 passing (these schema-driven tests
+exercise every `PAID_SERVICES` entry automatically, no new hardcoded cases needed per service).
+All 17 routes confirmed present in `/openapi.json` and `/.well-known/x402.json` with Solana
+listed first in every `accepts[]`/challenge. Live, real (non-fabricated) free-lane responses
+captured from every one of the 8 services' actual upstream: Open-Meteo (weather-guard-forecast),
+UK Carbon Intensity (carbon-now), RDAP (domains-check), arXiv/Crossref/Semantic Scholar
+(research-search), OpenLibrary/Gutenberg (books-search), MBTA GTFS (transit-plan: a real
+South-Station-to-Harvard Red Line itinerary), OSM Overpass (places-search: a real Starbucks
+near Boston), and GDELT (news-wire-query: a genuine 200 and a genuine 429, the latter
+confirming GDELT's documented ~1-req/5s throttle on this shared sandbox IP is real upstream
+behavior, not an app bug). `npm run check:rules --paths <every touched file>` exits 0 on all
+three commits; em-dash/en-dash grep clean on every new/changed line.
+
+No owner-gated action in this order: every step is code, tests, docs, and a local build; no
+other-crypto-project reference landed in the diff, so no batched owner ask was needed either.
+
+Commits: `b239cb926` (weather-guard), `228dafe28` (carbon), `92cd17eb6` (domains), `506cf74c7`
+(research), `0ecc3007c` (books), `48d05d9a7` (news-wire, transit, places), `ad01ea88a`
+(openapi.json free-tier-discoverability fix), `e18987975` (docs + changelog), this closing
+commit (PROGRESS log, order-file removal).