Built for humans
Static limits and MCC blocks can't say "buy this, for this purpose, this week, from these merchants."
Authorization for AI agent spend
Agents act.
Levee decides.
Levee lets a human approve what an AI agent may spend, enforces it at the moment of authorization, and keeps tamper-evident proof of every decision.
Payment requestCard authorization
- Agent
- procurement-bot
- Merchant
- AWS
- MCC
- 5734
- Amount
- $412.00 USD
LeveeMandate · policy · declaration
APPROVE
Within mandate: merchant, purpose and budgetWITHIN_MANDATE
- Fail-closed by default
- Passkey-signed mandates
- Hash-chained evidence
The problem
Agents got cards. Controls didn't keep up.
All-or-nothing keys
A prompt injection or a bug can drain a card or a wallet.
No proof
When an agent overspends or a charge is disputed, nobody can show which agent, run and approval led to it.
How it works
From a human's approval to a provable decision, in six steps.
Every payment an agent makes passes through Levee inside the authorization path, checked against what a person actually signed.
-
1
Mandate
A human signs a passkey-based mandate defining the agent, purpose, budget, allowed merchants, tokens or recipients, and expiry.
-
2
Declaration
The agent declares what it is about to do. A declaration can narrow permission, never expand it.
-
3
Enforcement point
The payment reaches Levee inside the authorization path, outside the agent, so it cannot be bypassed.
-
4
Decision
Policy + mandate + declaration produce approve, decline or challenge. Strictest wins. Timeout fails closed.
-
5
Challenge
Exceptional spend triggers a passkey step-up to the human.
-
6
Evidence
Inputs and decision are written to a hash-chained evidence ledger.
Every decision is explicit, reasoned and recorded.
Each response names the outcome, the reason, the mandate and policy version it was judged against, and its place in the ledger.
- APPROVEInside the mandate and policy.
- DECLINEOutside them, or no answer in time.
- CHALLENGEExceptional: the human confirms with a passkey.
Product
One product, three parts.
Spend Mandates
Structured, passkey-signed approvals that say exactly what an agent may do.
- Purpose, budget, merchants or categories, time window and which agent
- Designed to be compatible with Google AP2 mandates and Mastercard Verifiable Intent
Decision Engine
Policy, mandate and declaration evaluated together; returns approve, decline or challenge.
- Design target under 1 second p99
- Fail-closed
- Rate-limited challenges
Evidence Ledger
Tamper-evident records of every decision, with one-click evidence packs for chargebacks, finance review and audits.
- Tamper-evident, hash-chained audit ledger
- Cryptographic checkpoints
- Signed decision records
Rails
One decision core. Every rail.
Cards
Levee sits in the issuer or platform's real-time authorization webhook: amount, merchant, MCC, currency.
Works alongside issuers such as:
- Lithic
- Stripe Issuing
- Highnote
- Marqeta
- Airwallex
- Levee never issues cards, holds funds or settles payments.
Stablecoins
Levee as a required co-signer for agent wallets: a smart-account multisig signer, a delegated session-key authority, or an x402 facilitator check.
- Transaction simulation on actual balance changes
- Token, recipient and program policies
- Optional on-chain anchoring of ledger checkpoints
Same mandates, same policy, same ledger, whichever rail your agents pay on.
Who it's for
For platforms putting agents in charge of money.
Card-issuing platforms
AP and procurement software
Agent platforms
Wallet and payment infrastructure
x402 services
Stablecoin card programs
Why Levee
A neutral layer that adds what the alternatives leave out.
| Alternative | What it does | What Levee adds |
|---|---|---|
| Issuer-native rules | Static limits and MCC rules, tied to one issuer | Purpose-bound mandates that work across issuers |
| Agent cards from a single provider | Controls only on their own cards | Works on your card program |
| Full-stack agent payments | Controls bundled with their rails | A neutral layer, no switching rails |
| Approve/decline APIs | Rules and reason-coded logs, often fail-open | Human-signed mandates, fail-closed, hash-chained evidence |
| Pre-payment checks | Checks before the payment call | Enforced at authorization, can't be bypassed |
Design partner program
Become a design partner.
A free pilot for a small group of platforms putting AI agents in charge of spend.
What you get
- Sandbox integration on your issuer or rail
- Mandates and policies tuned to your agent workflows
- Sample evidence packs
- Support from the founding team
In return
- Honest feedback
- A go or no-go decision at the end
Become a design partner
We share the full pilot plan once we connect. Or write to hello@levee.dev
Team
Built by engineers who've shipped security-critical infrastructure.
Muhammed Irfan Kamaludeen
Co-founder
Vijayendra Gaur
Co-founder
FAQ
Questions about AI agent spend controls.
What is Levee?
Levee is an authorization layer for AI agent spend. A person approves what an agent may buy, Levee checks every payment against that approval at the moment of authorization, and each decision is recorded as tamper-evident evidence.
How is Levee different from card limits and MCC blocks?
Static limits and merchant category blocks can't express intent. Levee evaluates a signed spend mandate, the platform's policy and the agent's declared purpose together, so a payment is approved only when it matches what a human actually agreed to.
Where does Levee sit in the payment flow?
Levee runs inside the issuer's real-time authorization path, outside the agent. The agent can't skip or override it, and if a decision can't be made in time the payment fails closed.
Does Levee hold funds or issue cards?
No. Levee works alongside your existing card issuer or payment rail. It decides whether an agent's payment should go through and keeps the proof; money movement stays with your provider.
What happens when a payment falls outside the mandate?
Levee declines it, or sends a challenge to the human for a quick approval, depending on the policy. Every outcome comes with a reason code, and organization-level denies can't be overridden.
Which payment rails does Levee support?
Levee is built around one decision core for cards and stablecoin payments, so the same mandates and policies apply across rails.
Who is Levee for?
Card-issuing platforms, AP and procurement software, agent platforms, wallets and x402 services that let AI agents spend money on behalf of people or companies.
How can my company try Levee?
We're running a free design partner pilot with a small group of platforms. Write to hello@levee.dev and we'll share the pilot plan.