One API for disputes on every processor

Every call takes your store’s API key as a Bearer token: Authorization: Bearer zv_live_…. Make one in Settings, Connections, under “Your product (usage API)”. It is shown once. Requests are JSON unless they say otherwise, bodies are capped at 1 MB, and each endpoint has a per-minute limit that answers 429 with Retry-After.

When an AI agent buys for your customer and the card is later disputed as “I didn’t authorize this”, the customer’s grant to the agent is the evidence. Send each grant (a mandate: what the agent may buy, up to how much, until when, and how the customer confirmed it) and each purchase made under it. Field names follow the Agent Payments Protocol’s intent and cart mandates and the Agentic Commerce Protocol, and plain names work for any agent platform.

curl https://zevron.ai/api/v1/agent-mandates \
  -H "Authorization: Bearer zv_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "mandates": [{
      "id": "im_77", "email": "ana@example.com", "granted_at": "2026-09-01T10:00:00Z",
      "protocol": "ap2", "agent": "Acme Assistant",
      "instruction": "Reorder my espresso beans when I run low, up to $40 a time",
      "max_amount": "40.00", "currency": "USD", "merchants": ["example.com"],
      "expires_at": "2027-03-01T00:00:00Z", "authentication": "passkey",
      "signature": "<the signed mandate>"
    }],
    "purchases": [{
      "id": "cm_912", "email": "ana@example.com", "purchased_at": "2026-10-03T08:12:00Z",
      "mandate_id": "im_77", "order_id": "1042", "amount": "36.00", "currency": "USD",
      "user_confirmed": false
    }]
  }'

On a dispute we match the purchase by order, charge, or customer and amount, and check it against the grant: made before the purchase, within the limit, not expired or revoked, at a store the grant allows, confirmed with a passkey, 3-D Secure, a signature or the customer’s approval of the cart. A purchase inside the grant becomes the lead exhibit. One outside it is never argued: the case is marked to refund instead, because the customer is right. Signatures and credentials are kept only as a SHA-256, and card fields are dropped.

The MCP server lets Claude, ChatGPT or any MCP client answer “which disputes are due this week?”, “how much did we recover in September?”, “what wins a Visa 10.4 on Stripe?” or “which agent purchases went over the customer’s limit?”. Read tools: list_disputes, get_dispute, get_recovery_summary, get_prevention_findings, get_network_benchmarks, list_agent_purchases, get_deflection_stats. Two tools add evidence: record_agent_mandate and add_document (a PDF or image, which re-drafts an unfiled response). Nothing here files, approves or refunds: that stays with a person.

{
  "mcpServers": {
    "zevron": {
      "type": "http",
      "url": "https://zevron.ai/api/mcp",
      "headers": { "Authorization": "Bearer <your case-link token>" }
    }
  }
}

GET /api/v1/benchmarks?family=fraud&processor=stripe&network=Visa&reason_code=10.4 returns the win rates pooled across stores that speak to that kind of dispute, each with a 95% interval, and the evidence that adds most to the win rate. Only numbers with at least five stores and twenty decided disputes behind them are published. The same numbers are public at State of Disputes.