built for the agent economy

Give your agents a budget, not a credit card.

Paytoll sits between your AI agents and your money. Agents ask permission to spend; your policies decide; approved purchases get a single-use virtual card that expires in 15 minutes. Your real card never enters the conversation.

Request early access How it works

claude → paytolllive

›authorize_purchaseMarriott · $189 · travel

✓merchant allowed

✓$189 ≤ $200 per-transaction

✓$189 of $500 daily budget

⏳over $150 — owner approval

✓approved by owner

✓ card issued•••• 2522 · expires 15:00

How it works

Three moving parts. No stored card numbers.

Agent asks

One API call — or one MCP tool for Claude. The agent states merchant, amount, and a reason. It never touches payment credentials.

Policy decides

Daily limits, per-transaction caps, category allowlists, blocked merchants, approval thresholds. Every decision returns a rule-by-rule audit trail.

Card appears — then disappears

Approved purchases mint a single-use virtual card capped at the approved amount, dead in 15 minutes. Big amounts ping a human first.

The API

Every decision explains itself.

One endpoint to authorize spend. The response shows exactly which rules passed, the math behind the limits, and the card — so you can audit every dollar your agents touch, prompt included.

Ships with an MCP server: Claude gets authorize_purchase, get_limits, and friends out of the box. Integration takes minutes, not sprints.

authorize → decision → cardhttp

POST /v1/authorize
{
  "agent": "travel-agent",
  "merchant": "Marriott",
  "amount": 189.00,
  "category": "travel",
  "reason": "Deluxe King, 1 night",
  "prompt": "Book me a room near the venue for Friday"
}

→ 200 OK
{
  "approved": true,
  "decision": {
    "rules": [
      { "rule": "blocked_merchants",         "pass": true },
      { "rule": "allowed_categories",        "pass": true },
      { "rule": "single_transaction_limit",  "pass": true,
        "detail": "$189.00 vs limit $200.00" },
      { "rule": "daily_limit",               "pass": true,
        "detail": "$0.00 + $189.00 vs limit $500.00" }
    ]
  },
  "card": { "last4": "2522", "expires_in_seconds": 900 }
}

The card

Born for one purchase.
Dead in fifteen minutes.

01Every approval mints a fresh virtual card — one merchant, one purchase, capped at the approved amount plus a tax buffer.

02Fifteen minutes later it no longer exists. A leaked card number from an agent's context is worthless by the time anyone reads it.

03Your real card is never issued to an agent, never stored, never in the loop.

Why Paytoll

Not a payment rail. The control layer on top of one.

Card networks are racing to let agents pay. The question your business actually has is different: who approved it, against which budget, and why. That's the layer we build.

⏳

Humans stay in the loop

Set a threshold and big purchases pause for a one-tap owner approval — not machine-approves-machine. A compliance story your finance team already understands.

✓

Every decision explains itself

Rule-by-rule audit trails on every authorization — including the original prompt that triggered the spend. Answer “why did the agent buy this?” in one click.

Integrated in minutes

A REST API and a ready-made MCP server for Claude. Fiat-first — funded from your bank account, not a crypto balance. One developer, under 30 minutes.

Early access

Your agents are already spending.
Put a policy between them and your card.

We're onboarding a small group of teams building with agents. Tell us what you're building and we'll get you a sandbox.