Content Management
Content ManagementContent-Managementcontent-management
Providers using this tag (133)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 39 Usable, with meaningful gaps to close
Thin 34 Limited public surface area
Emerging 29 Early or largely undocumented
Minimal 9 Almost no public developer surface
APIs with this tag (76)
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 10 Complete, well-documented, and agent-ready
Strong 17 Solid coverage with minor gaps
Developing 16 Usable, with meaningful gaps to close
Thin 20 Limited public surface area
Emerging 13 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 133 providers in the APIs.io catalog tagged Content Management, 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 | 40.8 | 17.5 | +23.3 | 133 |
| Access Clarity | 41.8 | 22.3 | +19.5 | 133 |
| Developer Ergonomics | 34.7 | 17.9 | +16.8 | 133 |
| Operational Transparency | 26.2 | 11.3 | +14.9 | 133 |
| Discoverability | 69.5 | 60.4 | +9.1 | 133 |
| Contract Governance | 13.2 | 6.4 | +6.8 | 133 |
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) | 36% | 16% | +20 |
| MCP server (first-party) | 25% | 7% | +18 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 29% | 9% | +20 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 26% | 13% | +13 |
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 Marketing Cloud 83.5
- 2 Adobe 80.4
- 3 Optimizely 75.1
- 4 veeva 75
- 5 Bloomreach 73.7
- 6 Prismic 70.3
- 7 Acoustic 67.3
- 8 Showpad 66.2
- 9 Buffer 64.3
- 10 Coda Project 64.2
- 1 Automattic 62.3
- 2 Bloomreach 58.5
- 3 Salesforce Marketing Cloud 56.2
- 4 Coda Project 55.5
- 5 Genesys 55.1
- 6 Acoustic 53
- 7 Red Hat 52.3
- 8 Leadpages 50.6
- 9 Confluence 50
- 10 Spekit 50
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/content-management"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/content-management"
curl "https://apis.io/api/v1/cohorts/tag/content-management/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.