Omnichannel
Omni-ChannelOmni-channelOmnichannel
Providers using this tag (54)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 16 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 14 Early or largely undocumented
Minimal 5 Almost no public developer surface
APIs with this tag (13)
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 5 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 2 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 54 providers in the APIs.io catalog tagged Omnichannel, 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 | 37.9 | 17.5 | +20.4 | 54 |
| Access Clarity | 41.6 | 22.3 | +19.3 | 54 |
| Developer Ergonomics | 34.6 | 17.9 | +16.7 | 54 |
| Operational Transparency | 23.4 | 11.3 | +12.1 | 54 |
| Discoverability | 69.1 | 60.4 | +8.7 | 54 |
| Contract Governance | 13.4 | 6.4 | +7 | 54 |
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) | 30% | 16% | +14 |
| MCP server (first-party) | 13% | 7% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 26% | 9% | +17 |
| Security | 96% | 88% | +8 |
| Arazzo workflows | 9% | 2% | +7 |
| Governance rules | 28% | 13% | +15 |
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 83.3
- 2 Square 71.8
- 3 Infobip 71
- 4 Lucidya Ltd 68.7
- 5 SAP Emarsys 66.4
- 6 ServiceNow 64.8
- 7 Dotdigital 63.4
- 8 Crescendo Lab 59.1
- 9 Zendesk 58.1
- 10 Insider 57.6
- 1 Newstore 56.3
- 2 Salesforce 52.2
- 3 Infobip 47.7
- 4 Insider 46.4
- 5 Square 44.3
- 6 Dotdigital 41.8
- 7 Crescendo Lab 38.2
- 8 SAP Emarsys 37.9
- 9 Verifone 36.3
- 10 Zendesk 35.9
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/omnichannel"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/omnichannel"
curl "https://apis.io/api/v1/cohorts/tag/omnichannel/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.