Serverless
Serverlessserverless
Providers using this tag (140)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Developing 58 Usable, with meaningful gaps to close
Thin 31 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 6 Almost no public developer surface
APIs with this tag (91)
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 8 Complete, well-documented, and agent-ready
Strong 17 Solid coverage with minor gaps
Developing 41 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (33)
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 132 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 | 47.5 | 19.8 | +27.7 | 132 |
| Developer Ergonomics | 48.1 | 23.4 | +24.7 | 132 |
| Access Clarity | 45 | 26.5 | +18.5 | 132 |
| Operational Transparency | 32.3 | 14 | +18.3 | 132 |
| Contract Governance | 14.8 | 6.4 | +8.4 | 132 |
| Discoverability | 68.6 | 61.2 | +7.4 | 132 |
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) | 22% | 13% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 11% | +1 |
| Security | 97% | 97% | 0 |
| Arazzo workflows | 12% | 2% | +10 |
| Governance rules | 53% | 14% | +39 |
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 80.5
- 2 Amazon Web Services (AWS) 78.2
- 3 Oracle Cloud Infrastructure 71.1
- 4 Microsoft Azure Functions 68.6
- 5 fal 67.6
- 6 Netlify 67.3
- 7 Segmind 67.2
- 8 Cloudflare 65.1
- 9 Amazon API Gateway 64.9
- 10 Modal 64.4
- 1 Netlify 62.2
- 2 Insforge 57.7
- 3 Appwrite 54.5
- 4 Cloudflare 49.6
- 5 Oracle Cloud Infrastructure 42.5
- 6 Koyeb 39.8
- 7 IBM 37.3
- 8 Amazon Web Services (AWS) 37.2
- 9 Amazon EventBridge Scheduler 37.1
- 10 fal 36.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.