x402 payment gate (retired)
Historical: per-tool-call payment flow from the AI-assistant product.
x402 is an HTTP payment standard: a server answers 402 Payment Required with an invoice, the client pays, then retries with proof. Operator Uplift shipped an x402 gate as part of the prior AI-assistant product. This page documents what was built; the commitment-infrastructure product uses a different settlement path.
What was built (historical, AI-assistant era)
POST /api/tools/calendaror/api/tools/gmail, server returns402with aninvoice_referenceand pay endpoint.POST /api/tools/x402/paywith that reference, devnet simulated the on-chain transfer and marked the invoice paid.- Client retried the original request with
X-Payment-Proofheader. - Server validated the proof and executed the tool. Receipt anchored as a signed ed25519 envelope.
The flow was MCPay-compatible so MCP-aware agents could pay the gate without custom glue.
How commitment-infrastructure settles instead
The new product locks user stakes in escrow when a commitment is declared, then either returns the stake or redistributes it to the pool when the AI Game Master adjudicates a check-in. There is no per-tool-call invoice; there is a per-commitment settlement at the end of the cycle. The same ed25519 signing + Solana Merkle root + Filecoin/0G mirroring primitives carry forward as the trust stack.
The retired x402 tool routes (/api/tools/calendar, /api/tools/gmail, /api/tools/x402/pay) still exist in the codebase but are no longer the marketing happy path. The retired dashboard surfaces (PR #696, PR #709) bypass them entirely.