Telephony
Telephonytelephony
Providers using this tag (69)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 19 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (49)
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 6 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 21 Limited public surface area
Emerging 3 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 69 providers in the APIs.io catalog tagged Telephony, 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 | 49.9 | 17.5 | +32.4 | 69 |
| Developer Ergonomics | 44.5 | 17.9 | +26.6 | 69 |
| Access Clarity | 44.1 | 22.3 | +21.8 | 69 |
| Operational Transparency | 31.5 | 11.3 | +20.2 | 69 |
| Discoverability | 75.1 | 60.4 | +14.7 | 69 |
| Contract Governance | 20.3 | 6.4 | +13.9 | 69 |
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) | 51% | 16% | +35 |
| MCP server (first-party) | 26% | 7% | +19 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 25% | 9% | +16 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 25% | 13% | +12 |
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 Regal 79.6
- 3 Vapi 75.1
- 4 Leadping 72.2
- 5 Vessel 72.1
- 6 8x8 67.1
- 7 Weave 65.5
- 8 Gridspace 65.3
- 9 ServiceNow 64.8
- 10 Syllable 64.8
- 1 Sarj AI Developer API 60.4
- 2 Apollo.io 55.3
- 3 Genesys 55.1
- 4 The Mobile First Company 52.9
- 5 Salesforce 52.2
- 6 Happyrobot 51.6
- 7 AgentPhone 48.9
- 8 Swisscom 48
- 9 Regal 46.8
- 10 Webex 43.5
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/telephony"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/telephony"
curl "https://apis.io/api/v1/cohorts/tag/telephony/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.