Exchange
Exchangeexchange
Providers using this tag (79)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 28 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 6 Almost no public developer surface
APIs with this tag (32)
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 4 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 3 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 79 providers in the APIs.io catalog tagged Exchange, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 45.5 | 17.9 | +27.6 | 79 |
| Contract Quality | 39.1 | 17.5 | +21.6 | 79 |
| Operational Transparency | 30.3 | 11.3 | +19 | 79 |
| Access Clarity | 38.3 | 22.3 | +16 | 79 |
| Discoverability | 72.7 | 60.4 | +12.3 | 79 |
| Contract Governance | 16.4 | 6.4 | +10 | 79 |
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) | 43% | 16% | +27 |
| MCP server (first-party) | 16% | 7% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 15% | 9% | +6 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 30% | 13% | +17 |
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 Centers for Medicare and Medicaid Services 85.2
- 2 Salesforce 83.3
- 3 Stripe 83.2
- 4 Kraken 70.6
- 5 Bullish 67.3
- 6 Ripio 65.5
- 7 Factset 64.8
- 8 MediaMath 63.3
- 9 Slack 62.3
- 10 Blockchain.com 59.7
- 1 Factset 52.8
- 2 Salesforce 52.2
- 3 Copper.co 50.9
- 4 MediaMath 49.3
- 5 Stripe 47.8
- 6 SIX 46.2
- 7 Yieldmo 45.1
- 8 Lorum 44.8
- 9 Centers for Medicare and Medicaid Services 39.7
- 10 Forum 39.1
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/exchange"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/exchange"
curl "https://apis.io/api/v1/cohorts/tag/exchange/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.