200Lab
In 1997, HTTP reserved a status code almost nobody ever used: 402 Payment Required. Thirty years later, AI agents brought it to life: a machine requests, gets billed, settles on its own, and receives 200 OK— that five-character flip is the entire story of the agent economy, and the origin of this lab's name. We don't paraphrase protocol docs. We build them.
Toolbench
Everything you can actually use today. All publicly accessible unless noted, no signup required.
Payment Firewall Demo
Submit a payment and watch 11 gates rule on it before settlement: allow, review, or block.
Know-Your-Agent
KYC identifies people; agents need KYA. Check an agent's identity, operator and mandate.
Address Screening
Paste an on-chain address to screen it against OFAC and risk flags. Ethereum and Tron, no signup.
Proof Center
Every claim leaves a checkable trace: hash-chained audit log, GitHub witness, Bitcoin anchoring.
Responsible Agentic Payments
An open, protocol-neutral framework of seven pillars. Everything above implements it.
Integration Console
Register your agent, set its mandate, review verdicts and audit logs. For integrators.
Demo #1 · The Agent That Pays
Click run: an agent with a wallet is born in your browser and buys a piece of paid content from this site — every round-trip and signature actually happens. Open DevTools (F12 → Network) and watch the 402 with your own eyes.
Demo #2 · The Trust Layer That Blocks Bad Agents
If machines can pay on their own, bad agents can misbehave on their own. Between 402 and 200 we insert a trust layer — Know-Your-Agent + a policy firewall. Pick a scenario and watch it allow the good and block the bad, before settlement. A live reference of our Responsible Agentic Payments Framework.
Pick a scenario — watch the trust layer allow or block before settlement:
// run a scenario above
From demo to product
The two demos above aren't toys — behind them is the product OceanAlt is building: a compliant payment layer any agent can call. For humans it's the principle; for agents it's a capability.
Responsible Agentic Payments (RAP)
Seven pillars: KYA attribution, mandate & limits, firewall, AML screening, auditability, privacy, interoperability. Open, protocol-neutral.
Compliant Payment Tool (MCP)
oceanalt-mcp-pay: an MCP tool agents call natively — KYA + firewall + AML before settlement, so any agent can pay safely.
Compliant Payment Router
Aggregates settlement rails (x402/Circle/Stripe…) with a compliance layer on top — called once per agent payment.
What just happened
The agent requests a resource. The server doesn't ask who you are — it sends a bill: HTTP 402 with amount, payee, and a one-time nonce. No signup, no API key.
The agent signs an EIP-712 payment authorization with its own wallet — cryptographically unforgeable, and the key never leaves the agent.
The agent retries the same request with the signed credential in an X-PAYMENT header. To the server, this is money arriving.
The server verifies the signature, checks the quote, burns the nonce (single-use), releases the content and settles. 402 becomes 200. Done.