Backend-as-a-Service
Providers using this tag (32)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Developing 10 Usable, with meaningful gaps to close
Thin 11 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (7)
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 3 Limited public surface area
Emerging 1 Early or largely undocumented
Companies reaching this through an API (2)
These companies publish an API, specification or operation carrying “Backend-as-a-Service” 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 30 providers in the APIs.io catalog tagged Backend-as-a-Service, 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 | 43.9 | 23.4 | +20.5 | 30 |
| Contract Quality | 38 | 19.8 | +18.2 | 30 |
| Operational Transparency | 31.9 | 14 | +17.9 | 30 |
| Discoverability | 71.6 | 61.2 | +10.4 | 30 |
| Access Clarity | 35.8 | 26.5 | +9.3 | 30 |
| Contract Governance | 7.1 | 6.4 | +0.7 | 30 |
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) | 22% | 10% | +12 |
| MCP server (first-party) | 28% | 13% | +15 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 94% | 97% | -3 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 19% | 14% | +5 |
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.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.