System
Systemsystem
Providers using this tag (142)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 17 Solid coverage with minor gaps
Developing 55 Usable, with meaningful gaps to close
Thin 58 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (139)
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 2 Complete, well-documented, and agent-ready
Strong 17 Solid coverage with minor gaps
Developing 54 Usable, with meaningful gaps to close
Thin 57 Limited public surface area
Emerging 9 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 142 providers in the APIs.io catalog tagged System, 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 | 53.1 | 17.5 | +35.6 | 142 |
| Developer Ergonomics | 40 | 17.9 | +22.1 | 142 |
| Discoverability | 73.6 | 60.4 | +13.2 | 142 |
| Access Clarity | 34.9 | 22.3 | +12.6 | 142 |
| Operational Transparency | 23.8 | 11.3 | +12.5 | 142 |
| Contract Governance | 17.2 | 6.4 | +10.8 | 142 |
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) | 39% | 16% | +23 |
| MCP server (first-party) | 20% | 7% | +13 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 9% | +13 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 44% | 13% | +31 |
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 OpenMercantil 87.9
- 2 Treasure Data 76.7
- 3 Autoderm – AI Dermatology API 66.2
- 4 Factset 64.8
- 5 Cisco Catalyst SD-WAN 64.6
- 6 Palo Alto Networks 63.7
- 7 Cumulocity 63.2
- 8 Planable 62.3
- 9 Terabase Energy 61
- 10 Oracle Health (Cerner) 60.7
- 1 OpenGov 63.1
- 2 Terabase Energy 60.6
- 3 Sarj AI Developer API 60.4
- 4 Didit 56.7
- 5 Factset 52.8
- 6 Openwork 52.6
- 7 Planable 52
- 8 Treasure Data 48.4
- 9 Agnost AI 48.3
- 10 toksta 48.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/system"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/system"
curl "https://apis.io/api/v1/cohorts/tag/system/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.