Serverless
Providers using this tag (131)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 12 Complete, well-documented, and agent-ready
Strong 16 Solid coverage with minor gaps
Developing 49 Usable, with meaningful gaps to close
Thin 29 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 14 Almost no public developer surface
APIs with this tag (73)
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 20 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 26 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (31)
These companies publish an API, specification or operation carrying “Serverless” 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 126 providers in the APIs.io catalog tagged Serverless, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 43.2 | 17.6 | +25.6 | 126 |
| Developer Ergonomics | 45.9 | 23.2 | +22.7 | 126 |
| Operational Transparency | 32.1 | 13.7 | +18.4 | 126 |
| Access Clarity | 44.1 | 26.5 | +17.6 | 126 |
| Contract Governance | 13.8 | 6.3 | +7.5 | 126 |
| Discoverability | 64.1 | 58.1 | +6 | 126 |
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) | 29% | 14% | +15 |
| MCP server (first-party) | 25% | 12% | +13 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 11% | +3 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 15% | 2% | +13 |
| Governance rules | 55% | 14% | +41 |
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 Appwrite 83.2
- 2 Cloudflare 80.6
- 3 Amazon DynamoDB 80.3
- 4 Oracle Cloud Infrastructure 76.4
- 5 Prisma 72.7
- 6 Netlify 71.5
- 7 Amazon API Gateway 70
- 8 AWS Lambda 69.8
- 9 Microsoft Azure Functions 69.4
- 10 IBM 69.1
- 1 Cloudflare 72.5
- 2 Netlify 60
- 3 Insforge 57.7
- 4 Appwrite 54.5
- 5 Prisma 54.2
- 6 fal 50.6
- 7 Supabase 50.6
- 8 Oracle Cloud Infrastructure 49.3
- 9 Axiom 48.9
- 10 Vercel 45.7
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.