Compare / Markets / Telecommunications & Connectivity vs IoT & Connected Devices

compare_cohorts

Telecom vs IoT: the networks publish far better APIs than the devices on them

Telecommunications outscores IoT by 8.6 points, with 68 exemplars against 14. Part of the gap is our deeper coverage of telecom.

Telecommunications & Connectivity

31.6 average
thin on average
Agent readiness 18.9 · agent-aware
1259 scored providers · industry
VS

IoT & Connected Devices

23 average
emerging on average
Agent readiness 11.4 · agent-aware
992 scored providers · industry

Each sun is drawn from the cohort's averages: six facet rings, the mean Kin Score and mean agent readiness.

Check this first: the gap is partly our coverageTelecommunications & Connectivity scores 8.6 points higher than IoT & Connected Devices AND is the better-enriched cohort: 6 points less catalog_gap and 5 more artifact directories on the median member. The market difference and our coverage difference point the same way, so this delta cannot be attributed to the markets on its own. Close the enrichment gap, or report both figures together.

Telecom carriers and the connected devices that ride their networks are closely linked businesses, but they publish APIs very differently. The 1,259 scored telecommunications and connectivity providers average 31.6, against 23.0 for 992 IoT and connected-device companies. Telecom holds 68 exemplars to IoT’s 14, and its median of 30.0 sits well above IoT’s 17.6.

The lead runs across every facet: contract quality (28.9 against 17.1), developer ergonomics (34.9 against 25.1), operational transparency (22.4 against 12.9) and access clarity (32.0 against 23.7). Agent readiness follows, at 18.9 against 11.4, and 18% of telecom providers ship a first-party MCP server against 7% in IoT. Network APIs like CAMARA and the CPaaS providers have pushed telecom toward published, standard contracts. Device makers mostly have not followed.

depth_confounded is true, and by a meaningful margin: six points less catalog gap and five more artifact directories on the median telecom member. Treat the 8.6 points as partly ours.

The distributions

Telecommunications & ConnectivityIoT & Connected DevicesDelta
Kin Score, mean31.623+8.6
Kin Score, median3017.6+12.4
Kin Score, highest91.691.6
Kin Score, std dev20.417.1
Agent readiness, mean18.911.4+7.5
Agent readiness, highest80.580.5

Delta is Telecommunications & Connectivity minus IoT & Connected Devices, as the tool returns it.

Where the providers sit

Telecommunications & Connectivity

exemplar 68strong 141developing 233thin 276emerging 285minimal 256

IoT & Connected Devices

exemplar 14strong 44developing 138thin 164emerging 309minimal 323

Facet averages

FacetTelecommunications & ConnectivityIoT & Connected DevicesDelta
Discoverability 62.9 59 +3.9
Contract Quality 28.9 17.1 +11.8
Contract Governance 9 7.2 +1.8
Operational Transparency 22.4 12.9 +9.5
Developer Ergonomics 34.9 25.1 +9.8
Access Clarity 32 23.7 +8.3

What they publish

Share of each cohort's providers publishing each artifact. 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.

ArtifactTelecommunications & ConnectivityIoT & Connected DevicesDelta
First-party MCP server18%7%+11
Any MCP artifact (incl. derived)19%10%+9
OAuth scopes16%13%+3
Spectral rules23%16%+7
Arazzo workflows3%2%+1
Agent skills0%0%0
Security artifact97%99%-2

How well we know each cohort

The coverage behind the averages. A cohort with a higher catalog gap and fewer artifact directories has been enriched less, so part of any difference is our coverage rather than the market.

Telecommunications & ConnectivityIoT & Connected Devices
Declared members14321054
Scored (in the averages)1259 (88%)992 (94%)
Thinly covered1027880
Median artifact directories149
Mean catalog gap (points we could add)72.178.1
The full compare_cohorts response
{"a":{"kind":"industry","slug":"telecommunications","name":"Telecommunications & Connectivity","members":1432,"stats":{"kind":"industry","slug":"telecommunications","name":"Telecommunications & Connectivity","tier":"report","coverage":{"declared_members":1432,"resolved_members":1432,"scored_members":1259,"agent_scored_members":1259,"scored_share_pct":88,"unexamined_members":148,"enrichment_depth":{"mean_catalog_gap":72.1,"median_artifact_dirs":14,"n":1259,"thinly_covered":1027,"thinly_covered_of":1259,"thin_coverage_note":"1027 of 1259 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.","note":"Rubric points API Evangelist could add to the average member with no action by the providers, and the median count of artifact directories we hold on them. A cohort with a higher gap and thinner artifacts has been enriched less, so part of any difference between its mean and another cohort's is our coverage rather than the market. Compare two cohorts only when this figure is comparable. It is an upper bound on our backlog: it says who CAN close a gap, not who did."},"unexamined_note":"Excluded from the distribution: these carry a catalog-owned needs_work flag (never enriched, or no resolvable host). They are listed as members and keep their own page and score; they do not vote in the averages, because their score measures our coverage rather than their posture."},"sufficient":true,"kin_score":{"mean":31.6,"median":30,"min":0,"max":91.6,"stdev":20.4},"agent_readiness":{"mean":18.9,"median":19.6,"min":0,"max":80.5,"stdev":17.3},"band_distribution":{"exemplar":68,"strong":141,"developing":233,"thin":276,"emerging":285,"minimal":256},"facet_averages":{"discoverability":{"mean":62.9,"n":1259},"contract_quality":{"mean":28.9,"n":1259},"contract_governance":{"mean":9,"n":1259},"operational_transparency":{"mean":22.4,"n":1259},"developer_ergonomics":{"mean":34.9,"n":1259},"access_clarity":{"mean":32,"n":1259}},"adoption":{"mcp_pct":19,"mcp_first_party_pct":18,"mcp_note":"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.","skills_pct":0,"scopes_pct":16,"security_pct":97,"arazzo_pct":3,"rules_pct":23}}},"b":{"kind":"industry","slug":"iot","name":"IoT & Connected Devices","members":1054,"stats":{"kind":"industry","slug":"iot","name":"IoT & Connected Devices","tier":"report","coverage":{"declared_members":1054,"resolved_members":1054,"scored_members":992,"agent_scored_members":992,"scored_share_pct":94,"unexamined_members":54,"enrichment_depth":{"mean_catalog_gap":78.1,"median_artifact_dirs":9,"n":992,"thinly_covered":880,"thinly_covered_of":992,"thin_coverage_note":"880 of 992 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.","note":"Rubric points API Evangelist could add to the average member with no action by the providers, and the median count of artifact directories we hold on them. A cohort with a higher gap and thinner artifacts has been enriched less, so part of any difference between its mean and another cohort's is our coverage rather than the market. Compare two cohorts only when this figure is comparable. It is an upper bound on our backlog: it says who CAN close a gap, not who did."},"unexamined_note":"Excluded from the distribution: these carry a catalog-owned needs_work flag (never enriched, or no resolvable host). They are listed as members and keep their own page and score; they do not vote in the averages, because their score measures our coverage rather than their posture."},"sufficient":true,"kin_score":{"mean":23,"median":17.6,"min":0,"max":91.6,"stdev":17.1},"agent_readiness":{"mean":11.4,"median":2.5,"min":0,"max":80.5,"stdev":14},"band_distribution":{"exemplar":14,"strong":44,"developing":138,"thin":164,"emerging":309,"minimal":323},"facet_averages":{"discoverability":{"mean":59,"n":992},"contract_quality":{"mean":17.1,"n":992},"contract_governance":{"mean":7.2,"n":992},"operational_transparency":{"mean":12.9,"n":992},"developer_ergonomics":{"mean":25.1,"n":992},"access_clarity":{"mean":23.7,"n":992}},"adoption":{"mcp_pct":10,"mcp_first_party_pct":7,"mcp_note":"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.","skills_pct":0,"scopes_pct":13,"security_pct":99,"arazzo_pct":2,"rules_pct":16}}},"comparable":true,"delta":{"kin_score_mean":8.6,"kin_score_median":12.4,"agent_readiness_mean":7.5,"facets":{"discoverability":3.9,"contract_quality":11.8,"contract_governance":1.8,"operational_transparency":9.5,"developer_ergonomics":9.8,"access_clarity":8.3},"adoption":{"mcp_pct":9,"mcp_first_party_pct":11,"mcp_note":null,"skills_pct":0,"scopes_pct":3,"security_pct":-2,"arazzo_pct":1,"rules_pct":7},"enrichment_depth":{"mean_catalog_gap":-6,"median_artifact_dirs":5}},"depth_confounded":true,"depth_note":"Telecommunications & Connectivity scores 8.6 points higher than IoT & Connected Devices AND is the better-enriched cohort: 6 points less catalog_gap and 5 more artifact directories on the median member. The market difference and our coverage difference point the same way, so this delta cannot be attributed to the markets on its own. Close the enrichment gap, or report both figures together."}

Result read 2026-10-27. Telecommunications & Connectivity and IoT & Connected Devices each have their own page with the full roster and leaderboard.

Run this comparison yourself

Everything above came from one call to compare_cohorts. Swap in any two tags, industries, regions, areas or VC portfolios and you get the same answer for your own shortlist. It is an Understanding tool, included in the Understanding and Influence plans, or pay per call.

From any MCP client connected to https://apis.io/mcp:
{"name": "compare_cohorts", "arguments": {"a": "industry:telecommunications", "b": "industry:iot"}}
Over the REST API:
curl "https://apis.io/api/v1/cohorts/compare?a=industry:telecommunications&b=industry:iot" \
  -H "X-API-Key: $APIS_IO_KEY"
See the Understanding plan Connect the MCP server →

More comparisons

Work with this as data

Every comparison 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 market comparisons

5 MCP tools reach this
  • compare_providersUNDERSTANDING — two or more providers side by side: facets, artifacts, economics.
  • compare_cohortsUNDERSTANDING — two markets on one rubric, with the coverage check.
  • find_cohortsEvery scored population of providers in the catalog.
  • find_similar_providersProviders that look like a given one — a shortlist to compare.
  • gap_analysisINFLUENCE — what each provider is missing that the others publish.
All 92 tools →

Call it yourself

curl for this page
Compare two cohorts
curl "https://apis.io/api/v1/cohorts/compare?a=industry:payments&b=industry:banking" \
  -H "X-API-Key: $APIS_IO_KEY"
Find cohorts to compare
curl "https://apis.io/api/v1/cohorts?tier=report&limit=25" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

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.