React
Providers using this tag (59)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 21 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (51)
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 6 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 16 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 59 providers in the APIs.io catalog tagged React, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Operational Transparency | 27.7 | 11.3 | +16.4 | 59 |
| Contract Quality | 30.5 | 17.5 | +13 | 59 |
| Developer Ergonomics | 27.7 | 17.9 | +9.8 | 59 |
| Access Clarity | 31.1 | 22.3 | +8.8 | 59 |
| Discoverability | 68 | 60.4 | +7.6 | 59 |
| Contract Governance | 8.5 | 6.4 | +2.1 | 59 |
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) | 7% | 16% | -9 |
| MCP server (first-party) | 3% | 7% | -4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 5% | 9% | -4 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 39% | 13% | +26 |
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 Novu 66.6
- 2 Shopify 60.4
- 3 Fasten Health 59.2
- 4 Microsoft Power Apps 55
- 5 Livepeer 54.6
- 6 Trigger.dev 52.1
- 7 Speakeasy 51
- 8 Apollo GraphQL 49.4
- 9 CodeSandbox 45.7
- 10 Clerk 45.1
- 1 Stigg 42.4
- 2 Shopify 40.6
- 3 Fasten Health 38.5
- 4 Novu 34.2
- 5 Speakeasy 29.5
- 6 Self.ID 28.1
- 7 Trigger.dev 28
- 8 Apollo GraphQL 27.7
- 9 Microsoft Power Apps 27.3
- 10 Carto 26.8
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/react"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/react"
curl "https://apis.io/api/v1/cohorts/tag/react/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.