ZyroPay
ZyroPay is a non-custodial wallet where your AI can ask to pay, and you decide. An AI assistant (Claude, ChatGPT or any MCP client) connects to ZyroPay over OAuth. It can read balances and ask for payments, but it holds no key and neither does the server it talks to. Every request is checked against the policy you set for that agent, and by default you approve it with your passkey on a review of exactly what will be signed. On Cardano, ZyroPay pays HTTP 402 (x402) resources directly or into Masumi escrow, verifies the seller’s signed delivery receipt, and compares the result hash the seller records on chain with the bytes your agent actually received.
Design in five lines
Section titled “Design in five lines”- The agent asks; it never holds a key, and the MCP server it talks to cannot sign either.
Your policy decides first: which tools, wallets, networks, recipients and protocols, what USD limits, escrow above a threshold, registered sellers only.
Your passkey signs what you reviewed: the approval is bound to a SHA-256 of the payment’s terms, and the API refuses any other bytes.
On Cardano the payment is a plain x402 transfer, or a lock in Masumi escrow that the seller collects only after it records a result hash on chain.
ZyroPay checks the delivery: the seller’s signature over the exact bytes received, and their hash against the on-chain result, so you know when to ask for a refund.
The stack
Section titled “The stack”- TalkMCPYour AI asks over the Model Context Protocol. It holds no key.
- PermissionZyroPayYour policy and your passkey decide. The approval is bound to the exact payload.
- Paymentx402The seller quotes a price in an HTTP 402. ZyroPay builds the payment.
- TrustMasumi escrowThe money waits in escrow until the seller delivers. Refundable before it unlocks.
- RecordCardanoThe payment, the lock and the seller's result hash are on chain for anyone to check.
ZyroPay is the permission layer. MCP, x402, Masumi and Cardano are open technologies it uses; Turnkey holds the keys in secure enclaves, behind your passkey.
Proven on Cardano preprod
Section titled “Proven on Cardano preprod”| What happened | Transaction |
|---|---|
| First passkey-signed Cardano send from ZyroPay (1 ADA) | 0818000832…ef1ace (block 5353436, fee 0.167349 ADA) |
| ChatGPT paid an x402 report through ZyroPay (2 ADA), receipt verified | 83ecc5742f…9d787b (block 5353756, fee 0.167349 ADA) |
| An AI agent paid into Masumi escrow (5 ADA) | 630f20122b…43c653 (block 5353819, fee 0.187589 ADA) |
| The seller recorded its result hash; ZyroPay’s proof: verified | ee7b142e73…865361 (block 5353820, fee 0.688128 ADA) |
| A refund, a sub-hire, a registry registration | Awaiting live run |
Each transaction, with what to check on the explorer, is on the Evidence page. What is proven live and what only by tests is on Live vs tested offline.
Who it is for
Section titled “Who it is for”- People who want their AI to buy things such as data or API calls, without handing it a wallet, a seed phrase or a card.
- Agent builders who need a payment tool with a human in the loop, limits and an audit trail, over a standard MCP connector.
- Sellers of paid APIs on Cardano who want buyers that pay per request over x402 and can check what they received.
Status
Section titled “Status”- Test networks only. Cardano preprod, Solana devnet, Ethereum Sepolia and Base Sepolia, at https://app.zyropay.online. Production is not deployed.
- Not audited. No external security review has taken place. The threat model and its open items are in Security and trust.
- Cardano is passkey-only. An agent can never pay on Cardano without your approval: Turnkey cannot bound a Cardano signature with a policy, so autonomy is refused there. See Autonomous mode.
- Everything that is not yet proven live is listed in Limits and roadmap.