Markets · bedrock market · provisional
Telecom Network APIs (CAMARA)
Standards market. The Kin Score Market layer reads each provider in its market:
who it integrates with, how deep those integrations go, and where the market publishes its own structure.
Methodology.
25providers measured
8 (32.0%)declare their own
10 (40.0%)covered by others only
1 (4.0%)distribution only (sell through, not integrations)
6 (24.0%)undeclared
1declare compatibility (report only, not weighted)
0in-market workflows shown (10 bridges)
Provisional. Provisional and unweighted: the Market layer is not part of the composite or agent readiness. Leader lists are read within a position, never as one ranking. A provider that declares nothing we can
read is shown as undeclared, with no number: we never infer integrations.
Where this market publishes its structure
- CAMARA landscape (194 orgs) machine-readable
- CAMARA API-repo MAINTAINERS (maintains, not implements) machine-readable
- GSMA Open Gateway not machine-readable: 403
- Aduna availability not machine-readable: logo wall
- Nokia Network as Code supported networks not machine-readable: client-rendered
Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.
Leaders by position (provisional)
Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside
position, never inside it. Unknown-builder listings are left out of position shares and counted here.
coverage 7 · reaches banks, carriers, systems or channels (an aggregator)
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
| Twilio |
50.6 |
48 |
0 / 48 |
0 |
0 |
30 |
ipaas-bridge 75%, contract 8%, coverage 15%, covered 2% |
| Vonage |
48.5 |
7 |
0 / 7 |
0 |
0 |
0 |
standard 14%, coverage 71%, covered 14% |
| Infobip |
47.7 |
45 |
0 / 45 |
0 |
1 |
30 |
ipaas-bridge 67%, standard 2%, coverage 27%, covered 2%, distribution 2% |
| Sinch |
47.7 |
45 |
0 / 45 |
0 |
0 |
30 |
ipaas-bridge 71%, standard 2%, coverage 24%, covered 2% |
| Telesign |
41.7 |
4 |
0 / 4 |
0 |
1 |
0 |
coverage 75%, distribution 25% |
| Kaleyra |
30.7 thin |
2 |
0 / 2 |
0 |
0 |
0 |
coverage 100% |
| SignalWire |
15.3 thin |
1 |
0 / 1 |
0 |
0 |
0 |
coverage 100% |
covered 1 · reached mainly through aggregators
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
| Bandwidth |
19.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
covered 100% |
standard 9 · listed by a voluntary standard's own directory
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
| AT&T |
36.4 |
3 |
0 / 3 |
0 |
3 |
0 |
standard 25%, distribution 75% |
| Rogers Communications |
26.8 thin |
2 |
0 / 2 |
0 |
1 |
0 |
standard 50%, distribution 50% |
| Swisscom |
26.8 thin |
2 |
0 / 2 |
0 |
1 |
0 |
standard 50%, distribution 50% |
| Verizon |
23.6 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| América Móvil |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| KPN |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| Reliance Jio |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| Syniverse |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| TELUS |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
core 1 · builds the connectors its customers need
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
| Telnyx |
47.9 |
6 |
0 / 6 |
0 |
0 |
0 |
provider-built 50%, coverage 33%, covered 17% |
distribution 1 · only sells through cloud marketplaces
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
| Tata Communications |
9.6 thin |
1 |
0 / 1 |
0 |
1 |
0 |
distribution 100% |
undeclared 6 · declares nothing we can read: no number
Workflows
No in-market workflows yet; bridges: 10 (10 not yet mapped to a capability).
In-market workflows only: a step on the market provider's side maps to this market's business capabilities (BC-2640, BC-2660, BC-2700), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology.