Payments
PAYMENTSPaymentspayments
Providers using this tag (1623)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 36 Complete, well-documented, and agent-ready
Strong 152 Solid coverage with minor gaps
Developing 379 Usable, with meaningful gaps to close
Thin 365 Limited public surface area
Emerging 354 Early or largely undocumented
Minimal 337 Almost no public developer surface
APIs with this tag (999)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 26 Complete, well-documented, and agent-ready
Strong 135 Solid coverage with minor gaps
Developing 333 Usable, with meaningful gaps to close
Thin 291 Limited public surface area
Emerging 176 Early or largely undocumented
Minimal 38 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 1623 providers in the APIs.io catalog tagged Payments, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 30.8 | 17.9 | +12.9 | 1623 |
| Contract Quality | 30 | 17.5 | +12.5 | 1623 |
| Access Clarity | 30.2 | 22.3 | +7.9 | 1623 |
| Discoverability | 68.2 | 60.4 | +7.8 | 1623 |
| Operational Transparency | 17.9 | 11.3 | +6.6 | 1623 |
| Contract Governance | 10.5 | 6.4 | +4.1 | 1623 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 32% | 16% | +16 |
| MCP server (first-party) | 10% | 7% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 9% | +8 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 13% | 13% | 0 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Salesforce 83.3
- 2 Stripe 83.2
- 3 PAY.JP 78.6
- 4 Drippay 76.8
- 5 Squarespace 75.8
- 6 Highnote 75.4
- 7 Qonto 74.6
- 8 PayMongo 73.3
- 9 Unit 73.3
- 10 Spade 73.1
- 1 Primitive 75.2
- 2 Mollie 71.9
- 3 Agentcard 68.3
- 4 Drippay 68.3
- 5 Natural AI 67.6
- 6 Appcharge 62.5
- 7 ChargeAfter 60.2
- 8 Insforge 59.9
- 9 Goody 59.5
- 10 MonetizeNow 58.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/payments"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/payments"
curl "https://apis.io/api/v1/cohorts/tag/payments/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.