The office door
x402 — the office door. Every door in the portfolio answers a request for payment the same way: HTTP 402, the x402 standard, settled in USDC on Base, receipt signed and served forever. This is the office's own door, so a counterparty can prove the loop end to end with the principal's signature on the receipt. One resource: /api returns a signed statement of the office's current holdings summary. Price $0.01. Receipts at /x402/receipt/{nonce}, verified against /x402/jwks.json (kid mk-office-x402-2026-09). Settlement address and amount live in the 402 payload only. The office holds no cryptocurrency: the address is the rail's, the receipt is the office's. Facilitator: Coinbase Developer Platform. Network: Base mainnet.
What the call buys
- Route — https://agent-kg.ai/api · GET · 402 without payment, 200 with it
- Price — $0.01 USDC (10000 units) · Base mainnet eip155:8453 · asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
- Scheme — exact · EIP-3009 transferWithAuthorization · 60-second window · x402 v2
- Facilitator — Coinbase CDP (verify, settle) · Bazaar discovery extension on the 402
- Data — a signed statement of the office's current holdings summary (EdDSA, kid mk-office-x402-2026-09), drawn from /facts.json
- Receipt — EdDSA-signed, kid mk-office-x402-2026-09, key at /x402/jwks.json, resolves at /x402/receipt/{nonce}
- Receiver — configured (Worker secret; the address is on the 402 offer)
Paid calls
- Settled calls — counted from facilitator settlement receipts and held in KV for the office's own read; the count is not published (CEO ruling 2026-09-14)
- Last transaction — 0x7a83ac1714608801a2c6fb9ffc871e27a9c0d6e2133f9fbe24bf74c9f431357c
- Last receipt — https://agent-kg.ai/x402/receipt/0460f1eed51a70efe100d37eb4dfc7af
- As of — 2026-10-28T19:04:05.269Z
One call, one cent, one receipt
- 1 — GET /api. The answer is 402 Payment Required: the offer in the body and in the PAYMENT-REQUIRED header.
- 2 — Sign the payment (x402 v2, scheme exact) and repeat the call with the PAYMENT-SIGNATURE header.
- 3 — The facilitator verifies, the office answers { receipt, data }, the facilitator settles, and PAYMENT-RESPONSE carries the transaction.
- 4 — The receipt's jwt verifies against /x402/jwks.json; its receipt_url resolves forever.