REST
Providers using this tag (136)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 8 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 36 Usable, with meaningful gaps to close
Thin 53 Limited public surface area
Emerging 27 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (954)
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 66 Complete, well-documented, and agent-ready
Strong 44 Solid coverage with minor gaps
Developing 189 Usable, with meaningful gaps to close
Thin 302 Limited public surface area
Emerging 300 Early or largely undocumented
Minimal 53 Almost no public developer surface
Companies reaching this through an API (656)
These companies publish an API, specification or operation carrying “REST” 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.
Show all 656 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 136 providers in the APIs.io catalog tagged REST, 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 | 38 | 17.6 | +20.4 | 136 |
| Operational Transparency | 30.7 | 13.7 | +17 | 136 |
| Developer Ergonomics | 37.4 | 23.2 | +14.2 | 136 |
| Access Clarity | 39.5 | 26.5 | +13 | 136 |
| Discoverability | 67.1 | 58.1 | +9 | 136 |
| Contract Governance | 11.6 | 6.3 | +5.3 | 136 |
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) | 24% | 14% | +10 |
| MCP server (first-party) | 23% | 12% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 42% | 14% | +28 |
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 WSO2 79.9
- 2 Confluent | the Data Streaming Platform 77.3
- 3 Svix 76.7
- 4 Cvent Event Cloud 71.9
- 5 0xArchive 71.6
- 6 Amazon API Gateway 70
- 7 Canvas 68.2
- 8 Buildkite 68
- 9 StayingAPI 64.8
- 10 Benchling 64.5
- 1 0xArchive 66.9
- 2 Builder.io 64.2
- 3 StayingAPI 59.4
- 4 Newstore 59.2
- 5 Anvil 57.9
- 6 Smartling 57.1
- 7 Social Fetch 56.2
- 8 Plinth US Grants Data 54.9
- 9 Routebase 52.9
- 10 Buildkite 51.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.