Prototype Agent Payment Verification
Every agent payment, verified before it settles.
A payment can pass every allowlist and cap and still not be what the user asked for. MagiChain checks the merchant’s 402 terms, the spend rules and the user’s signed intent on the exact payment about to be signed. Intent, not just policy.
This opens your email app. Or write to [email protected]. We only use your email to reply (privacy).
See how it worksWhat each lock checks
Every payment passes each lock, in order, before it reaches the signer. One failed check stops it, with the reason.
Tool allowlist
The agent can only call the tools it was given.
Cashier rules
Approved shops, task budget, per-payment cap, duplicate check, rate limit.
Human approval
Payments above a threshold need a person’s yes.
x402 spend controls
The payment library’s own per-payment cap and token allowlist.
Price & terms check
The 402 must match: pay-to, token, price, validity window, resource.
Wallet policy
The wallet provider’s own signing policy.
AP2 intent mandate
The user signs what they want before the agent runs; every payment is checked against it.
Intent, not just policy
Compares each payment with what the user actually signed for, so a payment can pass every cap and still be stopped.
Built around x402
Sits in front of the wallet or signer you already use, as an extra layer on top of its own policy. A drop-in SDK is what early access is for.
Open standards
Works with x402, EIP-3009 and EIP-712 payments on Base, and with real AP2 intent mandates signed by the user.
Ready to see MagiChain in action?
We’re onboarding a small group of design partners building agentic payments and on-chain products.
This opens your email app. Or write to [email protected]. We only use your email to reply (privacy).