Payments has always been one of the most API-mature verticals — 264 providers across 1,778 APIs — but 2026 added a genuinely new actor to the flow: the agent that initiates the transaction. The plumbing was already there. What changed is who’s pulling the levers. This is post four in our week walking the hottest six industries on apis.io.
The bands
| Band | What it does | Providers on apis.io |
|---|---|---|
| Card & orchestration | Accept, route, settle payments | Stripe (57 APIs), Adyen (30), Square (37) |
| Banking data & open banking | Account, balance, transaction access | Plaid (39), TrueLayer |
| Accounting & ledgers | Reconcile, invoice, book | Intuit (8), Xero |
| Commerce & subscriptions | Catalog, billing, metering | Commerce Layer (3) |
Stripe’s 57 APIs are the clearest example of enterprise fragmentation in the whole catalog — Billing, Invoices, Payment Intents, Issuing, Identity, Climate, and Radar are all separate surfaces, split by operational role rather than by payment flow.
What’s shifted in 2026
- Agentic commerce arrived through MCP. Eleven of the top payment providers in the catalog now ship a Model Context Protocol server — Stripe, Adyen, Square, Intuit, Xero, TrueLayer, Commerce Layer, and others. That’s the infrastructure for letting an agent — not a human at a checkout — orchestrate a payment, subscription, or reconciliation without a bespoke integration each time.
- Fragmentation is a feature, not a mess. Stripe’s 57 and Adyen’s 30 APIs mean an agent (or a team) can call exactly the surface it needs — Payouts without Issuing, Billing without Radar — and the capability index makes that surface navigable across vendors instead of vendor-by-vendor.
- Usage-based billing went structural. Billing, Invoices, and Subscriptions show up as separate APIs at Stripe and Square. As software bills by consumption — including per-API-call agent cost — the metering layer is becoming its own micro-vertical inside payments.
Where to start
- The Payments industry page — the full cohort.
- capabilities.apis.io — compare charge, payout, billing, and KYC surfaces across providers.
- The MCP server catalog — the payment providers wired for agents.
- Provider profiles — Stripe, Adyen, Square, and Plaid are worth walking spec-by-spec.
The takeaway
Payments is where “agentic” stops being a slide and starts touching money. The catalog’s value here is that it shows the surface in operational pieces — the exact APIs an agent would call to move funds, check balances, or bill usage — and flags which vendors have shipped MCP to make that callable. If you’re designing for agents that spend, read the MCP column first, then the billing-and-metering band.