JSON:API
JSON APIJSON-APIJSON:API
Providers using this tag (27)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 16 Usable, with meaningful gaps to close
Emerging 3 Early or largely undocumented
Unrated 1 Not yet scored
APIs with this tag (10)
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 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 1 Early or largely undocumented
Companies reaching this through an API (5)
These companies publish an API, specification or operation carrying “JSON:API” 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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 26 providers in the APIs.io catalog tagged JSON:API, 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 | 49.8 | 19.8 | +30 | 26 |
| Developer Ergonomics | 47.9 | 23.3 | +24.6 | 26 |
| Operational Transparency | 32.1 | 13.9 | +18.2 | 26 |
| Access Clarity | 37.7 | 26.3 | +11.4 | 26 |
| Discoverability | 71.1 | 61 | +10.1 | 26 |
| Contract Governance | 11.4 | 6.3 | +5.1 | 26 |
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) | 19% | 10% | +9 |
| MCP server (first-party) | 15% | 9% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 37% | 11% | +26 |
| Security | 100% | 97% | +3 |
| Arazzo workflows | 7% | 2% | +5 |
| Governance rules | 11% | 14% | -3 |
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 Commerce Layer 70.8
- 2 Unit 69.1
- 3 Cobot 55.9
- 4 NationBuilder 55.2
- 5 Credo AI 50.3
- 6 Padlet 49.9
- 7 Decisiv 49.1
- 8 VergeSense 49.1
- 9 Jebbit 48.7
- 10 Opal 47.2
- 1 Decisiv 49
- 2 Padlet 47.7
- 3 Cobot 46.9
- 4 Beyond Pricing 40.5
- 5 Ankorstore 39
- 6 VergeSense 38.2
- 7 NationBuilder 35.8
- 8 Jebbit 35.8
- 9 Commerce Layer 34.7
- 10 Unit 32.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.