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(x402): document GET /api/x402/outbound-receipts and announce the Outbound tab
nirholasa1ef003113a5
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 5354adc83..32357fd94 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -14,6 +14,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **A generated SKILL-MD 1.0 catalog of every paid HTTP route is now live at /.well-known/skill.md**: Any agent can now load one markdown file, https://three.ws/.well-known/skill.md, and get a conformant SKILL-MD 1.0 document (the x402-skill-md format) listing every priced endpoint on three.ws: method, path, price, parameters, and the Solana and Base payment rails it settles on, plus a sample 402 challenge body. The document is generated straight from the same OpenAPI catalog /openapi.json serves (api/_lib/skill-md.js reads the shared buildOpenApiDoc() builder and the real buildExactRequirements() rail logic, so the catalog and the live 402 challenge can never drift apart), and is linked from /.well-known/x402.json and llms.txt. Validated in tests/skill-md.test.js against the real upstream x402-skill-md npm validator: zero errors other than the EVM rail finding (SM005), which is expected since this is a Solana-first platform and Base settles only when a facilitator is configured. Distinct from the pre-existing https://three.ws/skill.md (no .well-known), the Agent Skills connector file for installing three.ws MCP servers; both now cross-link to the other. (`/.well-known/skill.md`) `[feature, docs]`- **A spend call above an agent's approval threshold now pauses for the owner instead of failing**: The requires_approval verdict agent payment sessions and agent-to-agent hires can already produce now actually does something: both /api/pay/execute and /api/agents/a2a-hire create a request on the existing approval inbox the moment a call crosses the caller's approval_threshold_usd, answer with 202 and a poll link to /approvals/<id> instead of failing the call, and resume automatically the moment the owner taps Approve there, re-probing or re-running the exact same reserve-then-settle path the call would have taken inline, with no re-entry point for a double-spend. A denied request answers 403 on the next poll, an expired one answers 410, and retrying with the same idempotency key before the owner answers just re-polls instead of parking a second request. Nothing new to build on the approval page itself: it already renders any venue generically from the request's summary, amount, and risk notes, so the two new venues (payment_session_execute, a2a_hire) show up with the right Approve/Decline card for free. Covered by 21 new handler tests across create, approve, decline, expire, and the executor's own idempotent re-run. (`/approvals`) `[feature, security]`- **Payment sessions gain blocked hosts, an approval threshold, and a per-rail daily cap, all with tamper-evident verdicts**: Agent payment sessions get three new governance knobs, settable at creation and editable while a session is active: blocked_hosts (a denylist checked after the allowlist, so an explicit block always wins over a broad allow, even with no allowlist set), approval_threshold_usd (a call priced above this amount now gets a distinct requires_approval verdict instead of either settling or silently failing), and per_rail_daily_usd (a rolling 24h spend cap per settlement network, reserved atomically the same way the session budget already is, closing the race a naive sum-of-past-executions check would leave open). Every governance verdict, allow or reject, now carries a policy_digest (a sha256 hash of the exact policy it was judged against) and an HMAC signature over the verdict, digest, request, and timestamp, stored with the execution: editing a session's policy after the fact changes the digest and breaks the signature on every verdict that preceded the edit, so a verdict record can be trusted even after the policy it was judged against has since moved. The dry-run simulator at /api/pay/simulate now predicts all three new rules through the exact same shared policy module the real enforcer calls, so a simulated verdict and an enforced one can never disagree; that parity is pinned by a new test running both over identical scenarios. The payments page gained matching fields in both the session creation and edit modals, with inline validation and a collapsed 'Advanced spend policy' section so the common case (budget, expiry, host allowlist) stays uncluttered. (`/docs/payment-sessions`) `[feature, security]`+- **Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself**: The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts. (`/receipts`) `[feature]`## 2026-10-14diff --git a/data/changelog.json b/data/changelog.jsonindex 415a0a9ef..fac0f1caf 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,13 @@{"$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, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-10-15",+ "title": "Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself",+ "summary": "The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.",+ "tags": ["feature"],+ "link": "/receipts"+ },{"date": "2026-10-15","title": "17 named commerce tools and a spending report land in the x402 MCP buyer, hosted and self-custodial",diff --git a/docs/payment-sessions.md b/docs/payment-sessions.mdindex f429425e2..e411352f4 100644--- a/docs/payment-sessions.md+++ b/docs/payment-sessions.md@@ -363,6 +363,62 @@ max 100) and `cursor` pagination. Each item:`status` is `settled` or `failed`; failed rows carry an `error_code` (see theexecute error table below).+### `GET /api/x402/outbound-receipts`++The account-wide view across every session: what your agents spent at other,+external x402 merchants, enriched with what the Solana chain itself says+settled, not just what the merchant's response claimed. This is the+counterpart to [`GET /api/x402/my-receipts`](./x402-buyer.md) (what three.ws+billed a wallet); this endpoint answers what your agents spent elsewhere. It+backs the Outbound tab on [the Receipt Vault](https://three.ws/receipts).++Authenticates with the account session cookie or a bearer token scoped+`wallet:write` (the same credential `GET /api/pay/session/:id/executions`+accepts). Query params: `network` (`solana` or `base`), `host` (filter by+merchant host), `cursor`, `limit` (default 20, max 100).++```bash+curl -s "https://three.ws/api/x402/outbound-receipts?network=solana&limit=20" \+ -H 'authorization: Bearer sk_live_...'+```++```json+{+ "receipts": [+ {+ "id": "...",+ "sessionId": "...",+ "endpointUrl": "https://api.example.com/paid",+ "endpointHost": "api.example.com",+ "method": "GET",+ "network": "solana",+ "reportedAmountUsd": 0.05,+ "txHash": "5Kd...",+ "reportedPayer": "...",+ "reportedPayee": "...",+ "status": "settled",+ "createdAt": "2026-10-15T00:01:00.000Z",+ "resolved": {+ "payer": "...", "payee": "...", "mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",+ "amountAtomics": "50000", "decimals": 6, "feeLamports": 5000, "slot": 123456, "blockTime": 1792048039+ },+ "resolveError": null,+ "resolvePending": false+ }+ ],+ "nextCursor": null,+ "summary": { "total": 1, "totalSpendUsd": 0.05, "verified": 1, "unverified": 0, "uniqueMerchants": 1 }+}+```++`resolved` is the first-party settlement record, read straight from the+transaction's own token-balance change (payer, payee, mint, amount, fee, slot,+time) the first time anyone views that row, then cached. It is Solana-only for+now; a Base-network execution carries `resolved: null` and shows its reported+fields. `resolveError` is set if that resolution failed permanently (a code+like `tx_not_found`); `resolvePending` is true while a Solana row has not been+resolved yet.+### `PATCH /api/pay/session/:id`Update the mutable fields of an **active** session: `label`, `allowed_hosts`,@@ -563,4 +619,5 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd- [x402 Protocol](./x402.md): the challenge / verify / settle mechanics behind every paid call.- [x402 Buyer Client](./x402-buyer.md): paying x402 endpoints from your own wallet instead of a session.+- [Receipt Vault](https://three.ws/receipts): the Inbound/Outbound UI over `my-receipts` and `outbound-receipts`.- [x402 Developer Tools](./x402-dev-tools.md): free echo / debug / receipt-verification tools for debugging a paid call.diff --git a/docs/x402-buyer.md b/docs/x402-buyer.mdindex 35e5a6178..659f1e374 100644--- a/docs/x402-buyer.md+++ b/docs/x402-buyer.md@@ -112,3 +112,6 @@ guarantees: [Pending settlement](x402-settlement-pending.md).- [Autonomous x402 loop](autonomous-x402.md) — uses this client on a schedule.- [Pending settlement](x402-settlement-pending.md): the `settlement_pending`outcome, what a buyer does with it, and how the books close afterwards.+- [Payment Sessions](payment-sessions.md#get-apix402outbound-receipts): the+ outbound side of the ledger, what your agents spent at OTHER x402 merchants+ through a session, verified against the chain itself.diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 57fcc8f58..12308e188 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-10-15T06:54:02.716Z",+ "generated_at": "2026-10-15T07:31:13.188Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 4104,+ "total": 4105,"complete": false,"full_feed": "/changelog.json","entries": [@@ -93,6 +93,16 @@"security"]},+ {+ "date": "2026-10-15",+ "type": "update",+ "title": "Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself",+ "summary": "The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.",+ "link": "/receipts",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-14","type": "update",@@ -1549,16 +1559,6 @@"tags": ["launch"]- },- {- "date": "2026-10-10",- "type": "launch",- "title": "Import Skills",- "summary": "Install SKILL.md skills from any public GitHub repository or registry manifest. Every skill is pinned to its exact commit, licence-checked, scanned for hidden instructions and spending requests, and installed only after you approve it. Check imports for updates as a diff, fork any skill, and publish your own.",- "link": "/skills/import",- "tags": [- "launch"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex cf360693a..7eaad2df4 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-15T06:54:02.696Z",+ "generated_at": "2026-10-15T07:31:13.167Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -90,6 +90,16 @@"security"]},+ {+ "date": "2026-10-15",+ "type": "update",+ "title": "Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself",+ "summary": "The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.",+ "link": "/receipts",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-14","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex f0ececc30..60802c397 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -70,6 +70,14 @@<category>feature</category><description>Agent payment sessions get three new governance knobs, settable at creation and editable while a session is active: blocked_hosts (a denylist checked after the allowlist, so an explicit block always wins over a broad allow, even with no allowlist set), approval_threshold_usd (a call priced above this amount now gets a distinct requires_approval verdict instead of either settling or silently failing), and per_rail_daily_usd (a rolling 24h spend cap per settlement network, reserved atomically the same way the session budget already is, closing the race a naive sum-of-past-executions check would leave open). Every governance verdict, allow or reject, now carries a policy_digest (a sha256 hash of the exact policy it was judged against) and an HMAC signature over the verdict, digest, request, and timestamp, stored with the execution: editing a session's policy after the fact changes the digest and breaks the signature on every verdict that preceded the edit, so a verdict record can be trusted even after the policy it was judged against has since moved. The dry-run simulator at /api/pay/simulate now predicts all three new rules through the exact same shared policy module the real enforcer calls, so a simulated verdict and an enforced one can never disagree; that parity is pinned by a new test running both over identical scenarios. The payments page gained matching fields in both the session creation and edit modals, with inline validation and a collapsed 'Advanced spend policy' section so the common case (budget, expiry, host allowlist) stays uncluttered.</description></item>+ <item>+ <title>Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself</title>+ <link>https://three.ws/receipts</link>+ <guid isPermaLink="false">2026-10-15:Receipt Vault gains an Outbound tab: what your agents spent elsewhere, verified against the chain itself</guid>+ <pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The Receipt Vault at /receipts now has two tabs. Inbound is unchanged (what three.ws billed your wallet); the new Outbound tab answers the other question: what did your agents spend at OTHER x402 merchants while running on an Agent Payment Session. Each settled Solana execution is resolved against the settlement transaction's own token-balance change the first time anyone views it (payer, payee, mint, amount, fee, slot, time), independent of whatever the merchant's response claimed, then cached so later views are free; a 'verified' badge marks a row that matched the chain, 'pending' while resolution is still in flight, and 'unverified' if the lookup failed permanently. The tab is account-session gated (the same credential /payments uses, not a wallet signature, since Payment Sessions are account-scoped, not wallet-scoped), filters by network and merchant host, and exports to CSV alongside the existing JSON receipt downloads. New endpoint: GET /api/x402/outbound-receipts.</description>+ </item><item><title>8 keyless live-data services join the x402 paid API: weather, grid carbon, domains, research, books, news, transit, places</title><link>https://three.ws/docs/x402-endpoints</link>diff --git a/public/features.json b/public/features.jsonindex d95521c56..0fd6642b6 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-15T06:54:02.683Z",+ "generated_at": "2026-10-15T07:31:13.154Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",