Personalization
Providers using this tag (118)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 12 Complete, well-documented, and agent-ready
Strong 18 Solid coverage with minor gaps
Developing 22 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 20 Early or largely undocumented
Minimal 28 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (46)
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 7 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (20)
These companies publish an API, specification or operation carrying “Personalization” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 110 providers in the APIs.io catalog tagged Personalization, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 42.3 | 26.5 | +15.8 | 110 |
| Developer Ergonomics | 38.4 | 23.2 | +15.2 | 110 |
| Contract Quality | 29.8 | 17.6 | +12.2 | 110 |
| Operational Transparency | 25.9 | 13.7 | +12.2 | 110 |
| Discoverability | 65.2 | 58.1 | +7.1 | 110 |
| Contract Governance | 9.9 | 6.3 | +3.6 | 110 |
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% | 14% | +22 |
| MCP server (first-party) | 32% | 12% | +20 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 23% | 11% | +12 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 15% | 14% | +1 |
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 Algolia 82.8
- 2 Adobe Suite 78.3
- 3 Salesforce Marketing Cloud 77.3
- 4 Contentstack 75.1
- 5 Talon.One 74.3
- 6 Bloomreach 72.3
- 7 Mapp Marketing Cloud 70.4
- 8 MoEngage 69
- 9 Adobe Experience Cloud 68.2
- 10 Tealium 67.6
- 1 MoEngage 67.8
- 2 Algolia 66.5
- 3 Builder.io 64.2
- 4 Bloomreach 63.7
- 5 Cordial 62.9
- 6 Adobe Suite 62.3
- 7 Demandbase 60.6
- 8 Salesforce Marketing Cloud 57.9
- 9 Sendspark 56.8
- 10 Intelligems 55.2
Coverage caveat. 86 of 110 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 5 October 2026, across 29093 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.