Catalog
CatalogCatalogcatalog
Providers using this tag (489)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 19 Solid coverage with minor gaps
Developing 89 Usable, with meaningful gaps to close
Thin 106 Limited public surface area
Emerging 210 Early or largely undocumented
Minimal 54 Almost no public developer surface
APIs with this tag (513)
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 11 Complete, well-documented, and agent-ready
Strong 20 Solid coverage with minor gaps
Developing 94 Usable, with meaningful gaps to close
Thin 119 Limited public surface area
Emerging 217 Early or largely undocumented
Minimal 52 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 489 providers in the APIs.io catalog tagged Catalog, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 70.9 | 60.4 | +10.5 | 489 |
| Access Clarity | 30.3 | 22.3 | +8 | 489 |
| Operational Transparency | 18.7 | 11.3 | +7.4 | 489 |
| Contract Quality | 24.5 | 17.5 | +7 | 489 |
| Developer Ergonomics | 24.6 | 17.9 | +6.7 | 489 |
| Contract Governance | 9.1 | 6.4 | +2.7 | 489 |
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) | 25% | 16% | +9 |
| MCP server (first-party) | 16% | 7% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 9% | +13 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 19% | 13% | +6 |
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 HubSpot 82.4
- 2 RudderStack 80.2
- 3 MoEngage 75.8
- 4 Dynatrace 71.8
- 5 Square 71.8
- 6 NVIDIA NIM 71.2
- 7 fal 69.7
- 8 Virto Commerce 69.1
- 9 Mirakl 68.7
- 10 CleverTap 68.2
- 1 Mirakl 59.7
- 2 MoEngage 59.4
- 3 Hyperice 55
- 4 HubSpot 54.4
- 5 Brooklinen 53.1
- 6 Factset 52.8
- 7 Clawvisor 52.2
- 8 RudderStack 52
- 9 TikTok Marketing API 51.8
- 10 Liquid Death 51.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/catalog"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/catalog"
curl "https://apis.io/api/v1/cohorts/tag/catalog/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.