established · 1.2 market domain

Telephony

Score 25.9 / 100 76 providers +14 via APIs 33 APIs Search apis.io →
Business capabilities this tag reaches
Customer Service Management 2

Providers using this tag (76)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 5 Complete, well-documented, and agent-ready
Strong 20 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 7 Almost no public developer surface

APIs with this tag (33)

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 8 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 3 Early or largely undocumented

Companies reaching this through an API (14)

These companies publish an API, specification or operation carrying “Telephony” 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.

Apollo.io Cisco Collaboration Hybrid Solutions Concentrix DealerSocket Leadping LiveKit Pipecat Salesforce Salesforce Service Cloud APIs SendPulse ServiceNow Swisscom TPP (SystmOne) Webex

Score breakdown

Frequency
52.6
log-scaled weighted occurrences
Breadth
1.1
spread across providers
Quality lift
50.8
mean composite of providers using it
Cohesion
15.1
strength of nearest seed neighbor

Related tags

Contact Center 29 co-occurrences Phone Numbers 19 co-occurrences Voice 48 co-occurrences Voice Agents 12 co-occurrences Voice AI 20 co-occurrences Call Center 9 co-occurrences SIP 9 co-occurrences

Where this tag comes from

Provider tag76
Api tag33
Openapi tag4
Openapi op tag11

Cohort brief

Auto-generated

The 71 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.

Providers
71
of 76 in the catalog
Mean Kin Score
44.1
+21.3 vs catalog 22.8
Mean Agent Readiness
32.3
+19.0 vs catalog 13.3
Spread
4.5–77.2
median 47.9 · σ 18.2
How the 71 split by band
Exemplar 5Strong 20Developing 18Thin 16Emerging 8Minimal 4
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 51 25 +26 71
Contract Quality 43.3 18.2 +25.1 71
Developer Ergonomics 43.4 22.1 +21.3 71
Operational Transparency 27.9 12.4 +15.5 71
Contract Governance 21.2 9.4 +11.8 71
Discoverability 69.2 57.9 +11.3 71

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 34% 16% +18
MCP server (first-party) 35% 14% +21
Agent Skills 0% 0% 0
OAuth scopes 27% 13% +14
Security 94% 98% -4
Arazzo workflows 1% 2% -1
Governance rules 70% 35% +35

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.

Top by Kin Score
  1. 1 SignalWire 77.2
  2. 2 Microsoft Azure Communication Services 71.2
  3. 3 CloudTalk 68.3
  4. 4 Syllable 68.3
  5. 5 Avaya 66.5
  6. 6 Genesys 65.6
  7. 7 The Mobile First Company 65.2
  8. 8 Neutrino API 65.1
  9. 9 Phone Com 64.6
  10. 10 DialNexa 64.4
Top by Agent Readiness
  1. 1 Sarj AI Developer API 65.6
  2. 2 Speko 61
  3. 3 DialNexa 60.5
  4. 4 answeringservicecare-com 59.2
  5. 5 Simple AI 58.3
  6. 6 Phonic 57.9
  7. 7 Saperly 55.8
  8. 8 Synthflow 54.9
  9. 9 The Mobile First Company 54.5
  10. 10 Genesys 54.3
All 76 members of this roster resolve to a provider in the catalog; 71 carry a score (93%). The figures above describe the scored members only.
Coverage caveat. 41 of 71 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 7 November 2026, across 38912 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.

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.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/telephony"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.