What 90 kinds of apps are built on — Firebase and Sentry sit under 67 of them

What 90 kinds of apps are built on — Firebase and Sentry sit under 67 of them

apis.io has a new section, Applications. It takes 644 leading apps across 90 categories, from CRM and accounting to period trackers and mobile games, and reads what each one actually integrates with: the SDKs in its source, the integrations it lists, the trackers in its Android build. Every one of those integrations is joined to a provider in the catalog. The result is 2,911 distinct providers, 92.3% of them already profiled on apis.io, each row graded by how we know it — observed in the app’s own code or build, declared on its integrations page, or inferred, which is never counted.

The first finding is how much of every app is the same app. The shared layer ranks providers by how many categories use them. Firebase and Sentry each turn up in 67 of the 90. Stripe is in 57, Facebook in 52, Amazon S3 in 47 and Slack in 46. OpenAI is in 44 and Anthropic already in 39. Crash reporting, sign-in, payments, storage and messaging are not what makes a fitness app different from a CRM; they are the floor both stand on.

The second is that the floor is mostly ready for agents, and the gaps are specific. Nine of the twelve most-shared providers publish a first-party MCP server we could verify. The three that do not are Facebook, Apple and Google sign-in: identity and the platforms, the layer every app hands its users to. Of the 2,697 providers checked so far, 651 have a verified MCP server and 1,445 have confirmed none, after checking each one by hand against its own GitHub org and docs rather than trusting what a listing claims.

Each category is a blueprint you can read top to bottom. CRM & Sales Pipeline is eight reference apps, from HubSpot to Twenty, built on 54 providers, every one of them in the catalog, with a mean Kin Score of 58.1 and 32 verified MCP servers. The page splits the stack into the domain layer that makes it a CRM, the common layer it shares with everything, and the agent layer, and every row links the source it was read from. Each app has its own page too.

The capabilities come from the business capability model, now extended for apps. The enterprise model behind Business Capabilities describes what an organisation does, and had nowhere to put food databases, fitness tracking or agent payments. The API Evangelist extension adds 380 capabilities for consumer, B2B and agent products, credited separately from the Turbo EA model it builds on.

The pages are free; the data is on the Understanding plan. The category index is free at /api/v1/applications, and one category’s full blueprint, filterable by layer and evidence tier, is /api/v1/applications/<category>, also available to agents as the get_application_blueprint MCP tool. If your company is in a blueprint and the row is wrong, tell us and it gets fixed.

← Webhooks reach 658 providers, but only 85 show a way to resend one