Telnyx publishes 168 APIs on the network — more than Twilio’s 115 — and scores a composite of 36.8, in the thin band. Its agent-readiness score is 46.4 (agent-ready), and its agentic-access contract enumerates 1,038 operations, 553 acting, 61 human-in-the-loop.
Bigger surface, half the score. This profile is the clearest case in the catalog that those are unrelated measurements.
What is in the surface
Telnyx is a private-IP cloud communications platform: voice over SIP and programmable call control, SMS, MMS, fax, number management, IoT SIM, AI inference, and authentication. The catalog carries it resource by resource — Access Tokens, Addresses, Advanced Number Orders, Assistants, Audio, Audit Logs, Authentication Providers, Billing, Billing Groups, Brands, Bucket SSL Certificates, Bucket Usage, Bulk Phone Number Campaigns, Bundles, Call Commands, Call Control Applications, Call Information, Call Recordings, Campaigns, CDR Reports, and 148 more.
That is a real platform. Owning the network and selling the API on top of it is a genuinely different posture from reselling carrier capacity, and the surface reflects it — SIM management and number orders sit next to call control and AI assistants.
Where the 36.8 comes from
| Facet | Score |
|---|---|
| Contract quality | 64.3 |
| Discoverability | 40.7 |
| Commercial clarity | 36.8 |
| Operational transparency | 26.3 |
| Developer ergonomics | 13.0 |
| Governance | 0.0 |
Contract quality at 64.3 confirms the specs are real and callable. Everything else falls away, and two numbers do the damage.
Governance at 0.0. No published style guide, no machine-readable ruleset, no evidence of how 168 definitions are kept consistent with each other. Across a surface this size, that is not a paperwork gap — it is the reason the other facets drift.
Developer ergonomics at 13.0. Examples, getting-started paths, SDK signposting, the things that get somebody from documentation to a working call. On a platform whose competitor won the category on exactly this, 13.0 is the number that costs money.
The comparison that matters
Twilio: 115 APIs, composite 74.2. Telnyx: 168 APIs, composite 36.8.
Nobody chooses a CPaaS by counting endpoints. The 37-point spread is entirely in how the surface is explained, governed, and operated — and every point of it is fixable without shipping a single new endpoint. That is the good news buried in a thin score: the hard part, a large well-formed contract surface, is already done.
What 553 acting operations means
More than half of Telnyx’s operations mutate state — buying numbers, placing calls, sending messages, provisioning SIMs. 61 are marked human-in-the-loop, the highest ratio among the large CPaaS surfaces, and appropriately so: these are operations that spend money on every invocation and cannot be undone. A wrongly-sent SMS is delivered.
Takeaway
168 APIs, 1,038 operations, contract quality at 64.3 and governance at 0.0. Telnyx built the platform and skipped the paperwork that makes a platform usable by strangers. The 37 points between it and Twilio are documentation, governance, and ergonomics — not engineering.
See the full profile at apis.io/providers/telnyx/.