Content Delivery
Content Deliverycontent-delivery
Providers using this tag (36)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 8 Almost no public developer surface
APIs with this tag (21)
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 2 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 36 providers in the APIs.io catalog tagged Content Delivery, 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 | 36 |
| Developer Ergonomics | 30 | 17.9 | +12.1 | 36 |
| Operational Transparency | 20.3 | 11.3 | +9 | 36 |
| Access Clarity | 31.1 | 22.3 | +8.8 | 36 |
| Contract Governance | 13 | 6.4 | +6.6 | 36 |
| Discoverability | 65.6 | 60.4 | +5.2 | 36 |
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) | 22% | 16% | +6 |
| MCP server (first-party) | 11% | 7% | +4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 9% | +8 |
| Security | 89% | 88% | +1 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 36% | 13% | +23 |
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 Bloomreach 73.7
- 2 Prismic 70.3
- 3 Amazon CloudFront 55.3
- 4 Adobe Captivate 54.9
- 5 Storyblok 53.7
- 6 Ceros 51.6
- 7 Salesforce Experience Cloud 49.7
- 8 Signiant 48.9
- 9 Builder.io 48.1
- 10 Pruna AI 48.1
- 1 Bloomreach 58.5
- 2 Prismic 48.4
- 3 Adobe Captivate 36.7
- 4 Builder.io 35.4
- 5 Storyblok 34.9
- 6 Pruna AI 34
- 7 echo3D 32
- 8 Orange Business 31.7
- 9 Coorpacademy 31.5
- 10 Salesforce Experience Cloud 27.3
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-delivery"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/content-delivery"
curl "https://apis.io/api/v1/cohorts/tag/content-delivery/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.