Segments
Segmentssegments
Providers using this tag (76)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 24 Complete, well-documented, and agent-ready
Strong 19 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 5 Early or largely undocumented
APIs with this tag (80)
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 27 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 4 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 76 providers in the APIs.io catalog tagged Segments, 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 | 58.4 | 17.5 | +40.9 | 76 |
| Access Clarity | 56.8 | 22.3 | +34.5 | 76 |
| Developer Ergonomics | 51.1 | 17.9 | +33.2 | 76 |
| Operational Transparency | 43.9 | 11.3 | +32.6 | 76 |
| Contract Governance | 25.9 | 6.4 | +19.5 | 76 |
| Discoverability | 78.8 | 60.4 | +18.4 | 76 |
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) | 61% | 16% | +45 |
| MCP server (first-party) | 46% | 7% | +39 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 47% | 9% | +38 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 50% | 13% | +37 |
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 Customer.io 87.3
- 2 Kit 85.6
- 3 Mailchimp 81.5
- 4 OneSignal 78.3
- 5 MailerLite 77.2
- 6 SendGrid 77
- 7 Klaviyo 76.9
- 8 Treasure Data 76.7
- 9 Optimizely 75.1
- 10 Mapp Marketing Cloud 74.7
- 1 Boom Ai 71.9
- 2 Adobe Analytics 66.5
- 3 Automattic 62.3
- 4 Kit 61
- 5 Common Room 60.8
- 6 OneSignal 59.2
- 7 Mapp Marketing Cloud 56.3
- 8 Omnisend 54.3
- 9 Factset 52.8
- 10 NextRoll 52.2
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/segments"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/segments"
curl "https://apis.io/api/v1/cohorts/tag/segments/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.