πŸ€– Agent Commerce API Β· Beta

The rewards brain
every AI agent needs

One POST endpoint. Pass the user's cards and the purchase amount. Get back the best card to use β€” with reward rate, category, and a human-readable reason your agent can speak aloud.

320+
Credit cards in catalog
12
Spend categories
<80ms
p95 response time
300/min
Rate limit per key

Try it right now.

Select a merchant below and fire a real request to /v1/agent/recommend using our sandbox key.

POST /v1/agent/recommend
Request
Sandbox key
sp_agent_ca9e60e7_fea3cb05a72c8463d353166f1498726de5b2d6d151cb2fd6
Merchant
Request body
{
  "amount": 87.45,
  "mcc": "5411",
  "merchant_name": "Whole Foods",
  "cards": [
    {
      "id": "amex_blue_cash_preferred",
      "issuer": "American Express",
      "reward_type": "cashback",
      "base_rate": 1,
      "category_bonuses": [
        { "category": "groceries", "rate": 6 }
      ]
    },
    {
      "id": "chase_sapphire_preferred",
      "issuer": "Chase",
      "reward_type": "points",
      "base_rate": 1,
      "category_bonuses": [
        { "category": "dining", "rate": 3 },
        { "category": "travel", "rate": 3 }
      ]
    },
    {
      "id": "citi_double_cash",
      "issuer": "Citi",
      "reward_type": "cashback",
      "base_rate": 2
    }
  ]
}
Response
← Click "Run request" to see the live response

Add to your agent
in 10 minutes.

1

Get your key

Sign up below and verify your email. A sandbox sp_agent_sandbox_… key arrives instantly β€” no approval needed. Production (sp_agent_…) requires a quick review.

2

Pass the user's cards

In your agent's tool call, pass the user's cards[] array (id, issuer, reward_type, base_rate, category_bonuses) and the amount they're about to spend.

3

Use the recommendation

Read top_cards[0].reason β€” a human-readable string like "6% on groceries" β€” and pipe it directly into your agent's response. Done.

const res = await fetch('https://superpayrewards.com/v1/agent/recommend', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer sp_agent_xxxxxxxx_...',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    amount: 87.45,
    mcc: '5411',
    merchant_name: 'Whole Foods',
    cards: [
      { id: 'amex_gold', issuer: 'American Express', reward_type: 'cashback',
        base_rate: 1, category_bonuses: [{ category: 'groceries', rate: 6 }] },
      { id: 'citi_double_cash', issuer: 'Citi', reward_type: 'cashback', base_rate: 2 },
    ],
  }),
});

const { top_cards, category } = await res.json();
// top_cards[0].reason β†’ "6% on groceries"
// top_cards[0].estimated_reward_cents β†’ 524
// Hand this to your agent's LLM response directly.

Built for the agentic
commerce stack.

πŸ”

No user PII required

You send card metadata and a transaction amount β€” never an account number, cardholder name, or payment token. SuperPay never sees who is buying what.

⚑

Sub-100ms, always

Recommendations are computed from a cached catalog β€” no AI call in the critical path. Safe to call inline in a tool call without blowing your latency budget.

πŸ—£οΈ

LLM-ready reason strings

Every top_cards[].reason is a human-readable sentence your agent can speak aloud or embed in a chat response without post-processing.

πŸ’³

User-owned card portfolio

Pass the user's actual cards per-request. The engine scores each card against the transaction and returns a ranked list β€” no server-side state required.

πŸ”‘

Dedicated key namespace

Agent keys (sp_agent_…) are separate from merchant and bank keys β€” different rate limits, separate usage logs, independent rotation.

πŸ“Š

MCC + merchant resolution

Pass an MCC code, a category string, or a merchant name. The engine resolves whichever is most specific β€” no preprocessing on your side.

Start free, scale when you're ready.

Sandbox key (sp_agent_sandbox_…) is instant and free. Production key (sp_agent_…) requires a brief review β€” typically approved same day.

Production
By application
Apply below. We review your use case and origin domains before issuing a live key.
  • βœ“ sp_agent_… key β€” reviewed use case
  • βœ“ Everything in Sandbox
  • βœ“ Origin allowlist enforcement
  • βœ“ Key rotation via API
  • βœ“ Usage dashboard + audit log
  • βœ“ Production environment
Rate limit
300req / min
Applies to all production keys. High-volume partners can request a higher cap.
  • βœ“ 300 req / min per key
  • βœ“ MCC + merchant name resolution
  • βœ“ allowedCardProductIds filter
  • βœ“ Sub-100ms response time
  • βœ“ Raiseable for enterprise volume
  • βœ“ Per-key usage isolation