Twilio API

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

Twilio scores a C — solid on intent, parameters, and pagination (all 90%+), but completely absent on error handling. Of 197 operations, only one documents its error responses. Agents calling Twilio learn what happens on success but have no idea how to recover when a message fails to send or a phone number lookup returns 404.

Category breakdown

Examples50

Semantics65

Intent100

Error Handling0

Parameters99

Pagination90

Key findings

All 148 schemas lack examples
196 of 197 operations omit error response documentation
52 operations have missing or too-short descriptions
47 operations lack summaries
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 and add summaries to the 47 operations missing them.
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

Get API Key →