What is an AI agent payment mandate?
A mandate describes what a person allowed an AI agent to buy: maximum amount, currency, merchant, time window and purpose. The validator checks whether a proposed purchase still matches those boundaries.
FREE AI AGENT PAYMENT VALIDATOR
Check an AI purchase mandate before money moves.
Paste a sample or your own non-sensitive JSON. The tool explains whether the request stays inside the user's authority.
LOAD A SCENARIO
Live policy engine · no account · no card or personal data
READY
Change the purchase. See where authority ends.
Run one decision or test the same mandate against five boundary failures.
Developer mode: edit the complete JSON envelope
purchase-envelope.json
Sent only to this live sandbox
Ready for inspection
Run the sample or change a constraint to see the verdict.
Do not enter card data, bank credentials, private keys or personal information. Anonymous checks are not retained as transaction evidence.
What does a BLOCK mean?
At least one hard control failed—for example, the amount exceeds the limit, the merchant changed, consent is missing or the same purchase identifier was used before.
What does REVIEW mean?
No direct policy violation was found, but the envelope lacks evidence such as an intent hash, currency scope or agent identity binding. A human or stronger upstream check should resolve it.
FROM CHECK TO DEPLOYMENT
Put the same checks before your exclusive payment executor.
The free validator and MCP explain or project authority; neither can authorize execution or enforce provider egress. The API and CLI can support the lifecycle, but production enforcement exists only when you isolate provider credentials and alternate egress behind a customer-deployed exclusive executor.