Schema
Schemaschema
Providers using this tag (90)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 17 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (92)
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 5 Complete, well-documented, and agent-ready
Strong 13 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 28 Limited public surface area
Emerging 19 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 90 providers in the APIs.io catalog tagged Schema, 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 | 50.5 | 17.5 | +33 | 90 |
| Developer Ergonomics | 41.7 | 17.9 | +23.8 | 90 |
| Operational Transparency | 29.3 | 11.3 | +18 | 90 |
| Contract Governance | 19.9 | 6.4 | +13.5 | 90 |
| Access Clarity | 35.1 | 22.3 | +12.8 | 90 |
| Discoverability | 72.1 | 60.4 | +11.7 | 90 |
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) | 42% | 16% | +26 |
| MCP server (first-party) | 23% | 7% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 9% | +13 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 9% | 2% | +7 |
| Governance rules | 56% | 13% | +43 |
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 Salesforce 83.3
- 2 HubSpot 82.4
- 3 RudderStack 80.2
- 4 Optimizely 75.1
- 5 API Evangelist 69.8
- 6 SAP Emarsys 66.4
- 7 Celonis 66.2
- 8 Lytics 65.6
- 9 Factset 64.8
- 10 ServiceNow 64.8
- 1 HubSpot 54.4
- 2 Factset 52.8
- 3 Salesforce 52.2
- 4 Monetate 52
- 5 RudderStack 52
- 6 Celonis 51.8
- 7 Microsoft Azure 49.6
- 8 Lucid 48.3
- 9 API Evangelist 44.8
- 10 Autodesk 43.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/schema"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/schema"
curl "https://apis.io/api/v1/cohorts/tag/schema/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.