Usage
Usageusage
Providers using this tag (153)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 30 Solid coverage with minor gaps
Developing 68 Usable, with meaningful gaps to close
Thin 33 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (158)
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 12 Complete, well-documented, and agent-ready
Strong 32 Solid coverage with minor gaps
Developing 69 Usable, with meaningful gaps to close
Thin 34 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 153 providers in the APIs.io catalog tagged Usage, 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 | 55.4 | 17.5 | +37.9 | 153 |
| Developer Ergonomics | 46.4 | 17.9 | +28.5 | 153 |
| Access Clarity | 45.9 | 22.3 | +23.6 | 153 |
| Operational Transparency | 34.2 | 11.3 | +22.9 | 153 |
| Discoverability | 73.9 | 60.4 | +13.5 | 153 |
| Contract Governance | 16.5 | 6.4 | +10.1 | 153 |
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) | 49% | 16% | +33 |
| MCP server (first-party) | 23% | 7% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 23% | 9% | +14 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 15% | 2% | +13 |
| Governance rules | 38% | 13% | +25 |
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 ZoomInfo 80.8
- 3 Drippay 76.8
- 4 Commerce Layer 72.4
- 5 Leadping 72.2
- 6 Lusha 71.7
- 7 Mailosaur 71
- 8 ThousandEyes 70.2
- 9 fal 69.7
- 10 Cvent Event Cloud 69.6
- 1 Drippay 68.3
- 2 GC AI 58.8
- 3 Lusha 57.6
- 4 Apollo.io 55.3
- 5 Genesys 55.1
- 6 Red Hat 52.3
- 7 Salesforce 52.2
- 8 ThousandEyes 51.1
- 9 Twitter/X 50.6
- 10 Tigera 50.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/usage"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/usage"
curl "https://apis.io/api/v1/cohorts/tag/usage/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.