The Subscription Billing & Invoicing use case on apis.io scopes 35 providers. Stripe is not one of them. Neither are Chargebee, Recurly, Zuora, Lago or Metronome, all of which have records in the catalog. Ace Hardware and Urban Outfitters are. That is the finding, and it is ours to fix.
What changed since August
In August this page counted 35 providers and 822 APIs, led by Avalara at 75.7. The provider count is the same today. The API count is 228, the band mix has moved toward the middle (6 exemplar, 6 strong, 11 developing, 3 thin, 7 emerging, 2 minimal), and the top is now Airwallex at 83.8. Same headline number, a different set of facts underneath.
Who is in it
| Provider | Kin Score | Band | Agent Readiness |
|---|---|---|---|
| Airwallex | 83.8 | exemplar | 61.6 agent-native |
| WSO2 | 83.0 | exemplar | 35.4 agent-ready |
| Didomi | 80.0 | exemplar | 30.4 agent-ready |
| Token.io | 71.6 | exemplar | 53.6 agent-ready |
| Adyen | 71.1 | exemplar | 43.3 agent-native |
| Avalara | 69.9 | exemplar | 45.0 agent-ready |
| Amberflo | 46.5 | developing | 28.7 agent-ready |
Scores are from each provider file. Of the seven, only Amberflo is a billing engine in the sense a builder means: usage metering and pricing. WSO2 is an API management platform with monetization features. Didomi is consent management. Token.io is open-banking payments.
Further down, the list includes Ace Hardware (28.8), Urban Outfitters (26.0), Agilent Technologies (29.4) and Crystal Reports (24.5). Two members, management and monetization, are not companies at all; they are topic-collection records we created, and they score 9.6 and 8.6.
Who is missing
Stripe Billing would rank third in the use case if it were admitted. Chargebee, the company most people would name first for subscription management, would rank in the developing tier.
Why it happens
The use case matches on raw terms, 26 of them, from “API Monetization” to “Customer Invoicing”. Terms like “monetization” catch retailers with affiliate programs and analytics vendors with billing features, while the dedicated billing vendors evidently carry tags the matcher does not read. Membership by keyword rewards the vocabulary a record happens to use, not the job the company does.
Takeaway
For anyone building recurring billing today, the honest shortlist from the catalog is Stripe, Chargebee, Lago, Metronome, Recurly, Zuora and Amberflo for the engine, plus Avalara for tax, which is still the part that goes wrong. What would fix the page is on our side: admit the billing vendors by what they sell, drop the topic-collection records, and stop matching retailers on the word monetization.
See the use case at apis.io/use-cases/subscription-billing/.