Catalogs
Catalogscatalogs
Providers using this tag (37)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Emerging 3 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (48)
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 9 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 16 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 37 providers in the APIs.io catalog tagged Catalogs, 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 | 57.7 | 17.5 | +40.2 | 37 |
| Developer Ergonomics | 46.4 | 17.9 | +28.5 | 37 |
| Operational Transparency | 34.6 | 11.3 | +23.3 | 37 |
| Access Clarity | 42.2 | 22.3 | +19.9 | 37 |
| Contract Governance | 23.7 | 6.4 | +17.3 | 37 |
| Discoverability | 72.4 | 60.4 | +12 | 37 |
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) | 46% | 16% | +30 |
| MCP server (first-party) | 32% | 7% | +25 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 38% | 9% | +29 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 16% | 2% | +14 |
| Governance rules | 54% | 13% | +41 |
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 Klaviyo 76.9
- 2 Optimizely 75.1
- 3 Iterable 73.9
- 4 Talon.One 72.6
- 5 Infobip 71
- 6 Facebook Business Manager 68.6
- 7 Impact Radius 67.7
- 8 ServiceNow 64.8
- 9 Scryfall 57.2
- 10 Azure Databricks 56.5
- 1 Brainfish 58.8
- 2 Infobip 47.7
- 3 Klaviyo 47.5
- 4 Talon.One 45.2
- 5 Coveo 43.4
- 6 Tower 41.6
- 7 Facebook Business Manager 41
- 8 Optimizely 39.4
- 9 Impact Radius 38.8
- 10 Adobe Captivate 36.7
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/catalogs"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/catalogs"
curl "https://apis.io/api/v1/cohorts/tag/catalogs/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.