Agentic Payments
Agent PaymentsAgentic Payments
Providers using this tag (33)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (9)
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 →
Strong 1 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 1 Early or largely undocumented
Companies reaching this through an API (4)
These companies publish an API, specification or operation carrying “Agentic Payments” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 31 providers in the APIs.io catalog tagged Agentic 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 | 55.8 | 22.1 | +33.7 | 31 |
| Contract Quality | 43.9 | 18.2 | +25.7 | 31 |
| Access Clarity | 48.2 | 25 | +23.2 | 31 |
| Operational Transparency | 31.1 | 12.4 | +18.7 | 31 |
| Contract Governance | 26.2 | 9.4 | +16.8 | 31 |
| Discoverability | 73.2 | 57.9 | +15.3 | 31 |
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) | 81% | 16% | +65 |
| MCP server (first-party) | 81% | 14% | +67 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 35% | 13% | +22 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 84% | 35% | +49 |
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 Drippay 76.8
- 2 Natural AI 68.3
- 3 Lightspark 68
- 4 AnyAPI 64.8
- 5 Hilt 63.9
- 6 Pagesnap 61.8
- 7 x402 List API 59.9
- 8 ForceDream 59.8
- 9 Allowance 59.2
- 10 Orthogonal 53.2
- 1 AnyAPI 73.5
- 2 Natural AI 71
- 3 Allowance 67.6
- 4 1F916 66.4
- 5 Drippay 64.5
- 6 Hilt 64.5
- 7 ForceDream 51.5
- 8 Sponge 51.1
- 9 GetPaid 50.1
- 10 Lightspark 48.8
Coverage caveat. 19 of 31 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 7 November 2026, across 38912 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.