Recurring Billing
Providers using this tag (25)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Developing 8 Usable, with meaningful gaps to close
Emerging 4 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (15)
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 1 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 1 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 25 providers in the APIs.io catalog tagged Recurring Billing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 46.3 | 22.3 | +24 | 25 |
| Developer Ergonomics | 41.4 | 17.9 | +23.5 | 25 |
| Contract Quality | 39.5 | 17.5 | +22 | 25 |
| Operational Transparency | 28.8 | 11.3 | +17.5 | 25 |
| Discoverability | 70 | 60.4 | +9.6 | 25 |
| Contract Governance | 9.3 | 6.4 | +2.9 | 25 |
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) | 24% | 16% | +8 |
| MCP server (first-party) | 4% | 7% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 8% | 9% | -1 |
| Security | 96% | 88% | +8 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 32% | 13% | +19 |
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 Paystack 71
- 2 Efí Pay (Gerencianet) 70.6
- 3 HitPay 67.1
- 4 Paymob 61.6
- 5 Fat Zebra 56.2
- 6 Hotmart 52.1
- 7 Chargebee 50.3
- 8 Authorize.net 48
- 9 Worldpay 46.4
- 10 Bolt 45.5
- 1 Worldpay 44.8
- 2 HitPay 43.3
- 3 Verifone 36.3
- 4 Fat Zebra 33.6
- 5 CyberSource 33.1
- 6 Hotmart 27.3
- 7 Bolt 27
- 8 Authorize.net 26.1
- 9 Authorize.net 25.9
- 10 Paystack 25.1
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/recurring-billing"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/recurring-billing"
curl "https://apis.io/api/v1/cohorts/tag/recurring-billing/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.