apis.io now reads the catalog two ways that should agree, and in payments they do not. Markets holds a cohort of 25 payment providers, chosen as the market. Applications reads what 644 leading apps actually integrate with, from their code, their builds and their integration pages. Across the 61 app categories that take payments, those apps use 122 different payment-capable providers. Six of them are in the market cohort.
The overlap is the obvious names. Stripe is in 53 of the 61 categories and in the cohort. So are Square and Adyen. Then the lists part. PayPal is the second most-used payment provider in the apps we track, in 25 categories, and it is not in the cohort. Neither are Authorize.net (9 categories), Mollie (8, with a Kin Score of 72.2) or Braintree (7).
The other direction is just as stark. 19 of the 25 cohort members are used by none of the apps: banking-as-a-service and money-movement companies such as Cash App, Unit, Moov and Currencycloud. They are payment companies; they are not what an invoicing tool, a booking app or a storefront wires in at checkout.
Both lists are right about something different. The market cohort describes who builds payment infrastructure. The application blueprints describe who apps hand their customers to when it is time to pay. A buyer choosing a checkout provider wants the second list, and until now the catalog only offered the first. The same split shows up in other markets, and we are going through them one at a time, starting here.
What is in the evidence. Every row behind these numbers is graded: observed in an app’s own code or build, or declared on its integrations page. Inferred rows are never counted. Each provider page now shows which apps use it, under “Used by apps”, and each category blueprint links the source every row was read from.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.