Issue cards. Set limits. Let your AI pay.
4020 0000 0003 1011
CARDHOLDER
BACKEND BOT
EXPIRES
03/26
4020 0000 0002 6789
CARDHOLDER
DATA PIPELINE
EXPIRES
06/26
4020 0000 0001 2345
CARDHOLDER
AI ASSISTANT
EXPIRES
12/25
One rogue agent can drain your entire wallet in minutes
MCP and browser extensions require you to click "approve" for every payment
Can't limit who your agent pays or how much it spends per day
16-digit card number, expiry date, just like a real credit card. Create as many as you need.
Per-transaction cap, daily budget, total allowance. You decide how much your AI can spend.
Pause or revoke any card instantly. One click to stop all payments.
Create your first payment card in minutes
Set spending limits, daily budget, and recipient whitelist
A simple API key that lets your agent request payment signatures
Agent calls 402ok with payment requirements, we check limits and sign if approved
Allowance deducted, transaction logged, AI gets the resource it paid for
Built on the open x402 protocol for machine-to-machine HTTP payments. Learn more at x402.org
Raw Wallet: No limits. Agent can spend everything in one transaction.
402ok Card: Per-tx limit, daily cap, and total allowance. Triple protection.
Raw Wallet: Agent can pay anyone, anywhere, for anything.
402ok Card: Whitelist specific recipients. Block everything else.
Raw Wallet: Once compromised, funds are gone. No way to stop it.
402ok Card: Pause or revoke instantly. Your funds stay safe.
You don't give employees your bank account. You give them company cards with spending limits. Same idea for AI agents.
Claude, ChatGPT, custom agents. Give each one a card with a $10/day limit.
Cron jobs, data pipelines, automation scripts. Headless? No problem.
Pay-per-call APIs, premium data sources. Budget by project or client.
It's a virtual card you issue to an AI agent. Each card has a 16-digit number, expiry date, spending limits, and a Payment Key (API key) that lets the agent request payment signatures.
Your wallet has no limits. A card has per-transaction caps, daily limits, allowance budgets, and recipient whitelists. If an agent goes rogue, it can only drain the card's allowance—not your whole wallet.
Allowance is the pre-funded balance on a card. You add funds to the allowance, and each payment deducts from it. When it hits zero, the card stops working until you top up.
Yes. Each card has a whitelist. Add specific wallet addresses, and the card will only pay those recipients. All other payment requests are blocked.
All payment requests using that card's Payment Key are immediately rejected. You can resume anytime, or revoke permanently.
Base, X Layer, and more coming. We use USDC for payments via the x402 protocol.
We use HD wallet derivation. Your master seed generates unique addresses, and private keys are derived at runtime—never stored in the database.
Yes! We have an MCP endpoint for Claude and other MCP-compatible clients. But our HTTP API works with any client that can make REST calls.
Pricing details coming soon. Our goal: simple, transparent, pay-for-what-you-use.