REST
RESTRestrest
Providers using this tag (859)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 15 Complete, well-documented, and agent-ready
Strong 33 Solid coverage with minor gaps
Developing 142 Usable, with meaningful gaps to close
Thin 281 Limited public surface area
Emerging 334 Early or largely undocumented
Minimal 54 Almost no public developer surface
APIs with this tag (1063)
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 25 Complete, well-documented, and agent-ready
Strong 45 Solid coverage with minor gaps
Developing 177 Usable, with meaningful gaps to close
Thin 354 Limited public surface area
Emerging 409 Early or largely undocumented
Minimal 53 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 859 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 | 28.1 | 17.5 | +10.6 | 859 |
| Operational Transparency | 21.8 | 11.3 | +10.5 | 859 |
| Discoverability | 70.2 | 60.4 | +9.8 | 859 |
| Access Clarity | 31.4 | 22.3 | +9.1 | 859 |
| Developer Ergonomics | 24.9 | 17.9 | +7 | 859 |
| Contract Governance | 8.1 | 6.4 | +1.7 | 859 |
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% | 16% | -3 |
| MCP server (first-party) | 7% | 7% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 9% | +5 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 25% | 13% | +12 |
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 Xquik 92.3
- 2 Salesforce 83.3
- 3 Adobe 80.4
- 4 Svix 79.2
- 5 NextGen Healthcare 75.7
- 6 Adobe Suite 71.2
- 7 Hightouch 70.6
- 8 Kraken 70.6
- 9 Plinth US Grants Data 70.5
- 10 Heroic Labs 70.4
- 1 Xquik 82.9
- 2 Adobe Workfront 62.9
- 3 Adobe Suite 61.5
- 4 Hightouch 61.2
- 5 StayingAPI 59.4
- 6 Newstore 56.3
- 7 Hyperice 55
- 8 Equals 54.4
- 9 Read AI 53.6
- 10 Salesforce 52.2
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/rest"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/rest"
curl "https://apis.io/api/v1/cohorts/tag/rest/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.