REST
RESTRestrest
Providers using this tag (144)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 49 Usable, with meaningful gaps to close
Thin 51 Limited public surface area
Emerging 24 Early or largely undocumented
Minimal 2 Almost no public developer surface
Unrated 3 Not yet scored
APIs with this tag (1133)
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 132 Complete, well-documented, and agent-ready
Strong 73 Solid coverage with minor gaps
Developing 226 Usable, with meaningful gaps to close
Thin 325 Limited public surface area
Emerging 330 Early or largely undocumented
Minimal 47 Almost no public developer surface
Companies reaching this through an API (709)
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 709 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 141 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 | 40.3 | 19.8 | +20.5 | 141 |
| Operational Transparency | 30.4 | 14 | +16.4 | 141 |
| Access Clarity | 39.2 | 26.5 | +12.7 | 141 |
| Developer Ergonomics | 35.9 | 23.4 | +12.5 | 141 |
| Discoverability | 69.5 | 61.2 | +8.3 | 141 |
| Contract Governance | 12.1 | 6.4 | +5.7 | 141 |
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) | 13% | 10% | +3 |
| MCP server (first-party) | 20% | 13% | +7 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 18% | 11% | +7 |
| Security | 99% | 97% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 44% | 14% | +30 |
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 Svix 80.4
- 2 Canvas 73.7
- 3 Confluent | the Data Streaming Platform 72.9
- 4 0xArchive 72.7
- 5 Cvent Event Cloud 69.9
- 6 Benchling 69.6
- 7 Plinth US Grants Data 66.7
- 8 Buildkite 65.2
- 9 Amazon API Gateway 64.9
- 10 StayingAPI 63.6
- 1 StayingAPI 59.4
- 2 Newstore 59.2
- 3 0xArchive 57.7
- 4 Plinth US Grants Data 54.9
- 5 Svix 49.4
- 6 Confluent | the Data Streaming Platform 49.4
- 7 Routebase 47.5
- 8 Cvent Event Cloud 46.1
- 9 Social Fetch 45.7
- 10 Builder.io 45.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.