Telecommunications
Providers using this tag (220)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 13 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 33 Early or largely undocumented
Minimal 122 Almost no public developer surface
APIs with this tag (133)
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 →
Strong 7 Solid coverage with minor gaps
Developing 123 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 220 providers in the APIs.io catalog tagged Telecommunications, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 18.2 | 17.9 | +0.3 | 220 |
| Contract Governance | 6.6 | 6.4 | +0.2 | 220 |
| Operational Transparency | 10.7 | 11.3 | -0.6 | 220 |
| Discoverability | 59.2 | 60.4 | -1.2 | 220 |
| Contract Quality | 15.7 | 17.5 | -1.8 | 220 |
| Access Clarity | 15.8 | 22.3 | -6.5 | 220 |
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) | 21% | 16% | +5 |
| MCP server (first-party) | 5% | 7% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 9% | +5 |
| Security | 73% | 88% | -15 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 6% | 13% | -7 |
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 Zoom Phone 72.1
- 2 Infobip 71
- 3 8x8 67.1
- 4 Nokia Network as Code 65.7
- 5 ServiceNow 64.8
- 6 Swisscom 63.8
- 7 Verizon 62.8
- 8 KPN 61.9
- 9 GSMA 59.8
- 10 América Móvil 59.6
- 1 Zoom Phone 54.3
- 2 Telia Company 48.1
- 3 Swisscom 48
- 4 ETSI 47.9
- 5 EFFECT Photonics 47.7
- 6 Infobip 47.7
- 7 SK Telecom 43.7
- 8 8x8 43.3
- 9 Nokia Network as Code 43
- 10 GSMA 42.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/telecommunications"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/telecommunications"
curl "https://apis.io/api/v1/cohorts/tag/telecommunications/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.