Twilio API Autopsy: What Agent-Native Almost Looks Like

Twilio is the communications API that set the standard for developer DX. At 8.0/10 AN Score (L4 Established), it's one of the highest-scoring services in Rhumb's dataset. This autopsy examines what Twilio gets right for agents — and the friction points that keep it from a perfect score. Canonical post: rhumb.dev/blog/twilio-api-autopsy Score at a glance Dimension Score AN Score 8.0 / 10 (L4) Execution 8.4 Access Readiness 7.3 Confidence 63% Agent decision: Use Twilio as the default choice for agent-driven SMS, voice, and WhatsApp messaging. Authentication is trivial (SID + token), most operations are idempotent-safe, and error messages are specific enough for self-correction. Budget for carrier-level rate limiting, A2P 10DLC registration latency (1–7 days for US numbers), and per-destination pricing variability. This is one of the easiest high-value APIs for an agent to integrate. What makes Twilio agent-friendly 🔑 Authentication agents actually understand Account SID + Auth Token. Ba