Serverless
Serverlessserverless
Providers using this tag (174)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 25 Solid coverage with minor gaps
Developing 75 Usable, with meaningful gaps to close
Thin 41 Limited public surface area
Emerging 20 Early or largely undocumented
Minimal 11 Almost no public developer surface
APIs with this tag (75)
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 1 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 31 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 12 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 174 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 | 46.5 | 17.5 | +29 | 174 |
| Developer Ergonomics | 39.8 | 17.9 | +21.9 | 174 |
| Access Clarity | 40.2 | 22.3 | +17.9 | 174 |
| Operational Transparency | 27 | 11.3 | +15.7 | 174 |
| Discoverability | 69.3 | 60.4 | +8.9 | 174 |
| Contract Governance | 14.2 | 6.4 | +7.8 | 174 |
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% | 16% | +13 |
| MCP server (first-party) | 12% | 7% | +5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 9% | +5 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 14% | 2% | +12 |
| Governance rules | 55% | 13% | +42 |
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 Medplum 91.3
- 2 fal 69.7
- 3 Amazon API Gateway 65.8
- 4 Modal 65.1
- 5 Palo Alto Networks 63.7
- 6 IBM 62.6
- 7 Cloudflare 62
- 8 Freestyle 61.7
- 9 Amazon Web Services (AWS) 60.6
- 10 Koyeb 60.5
- 1 Insforge 59.9
- 2 Hugging Face Transformers 53.9
- 3 Medplum 50.8
- 4 Microsoft Azure 49.6
- 5 MongoDB 44.8
- 6 Cloudflare 44.5
- 7 Atlassian 41.9
- 8 Oracle 41.9
- 9 Shopify 40.6
- 10 IBM 39.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/serverless"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/serverless"
curl "https://apis.io/api/v1/cohorts/tag/serverless/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.