Twilio API

https://twilio.com · v1.0.0 · 197 operations · 148 schemas

Twilio scores 58, a D. Intent (100), parameters (99), and pagination (90) are excellent. But errors score 0. Not a single operation across the spec documents its 4xx or 5xx responses. Agents calling Twilio learn what happens on success and have no idea how to recover when a message fails to send or a phone number lookup returns 404. The other gap is examples on schemas: every one of the 148 schemas lacks them.

Category breakdown

Examples60

Semantics64

Intent100

Error Handling0

Parameters99

Pagination90

Key findings

32 of 197 operations lack request and response examples
All 148 schemas lack examples
All 197 operations omit error response documentation
52 of 197 operations have missing or too-short descriptions
97 of 148 schemas have no description

What Twilio should fix

Document error responses on every operation. The "happy path only" pattern is the single largest gap.
Add examples to all 148 schemas. Twilio's primitives (phone numbers, message SIDs, SIP URIs) have specific formats that examples teach faster than descriptions.
Expand the 52 short operation descriptions.
Describe the 97 schemas currently lacking descriptions.

How does your API score?

Run AgenticScore on your own OpenAPI spec — find issues before LLMs do.

npx agenticscore score ./openapi.yaml

Install the CLI →