Agent readiness · SMS, voice and messaging
twilio.com
12 of 16 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://www.twilio.com/llms.txt and https://docs.twilio.com/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript16,435 characters of text without JS, on https://www.twilio.com/docs/chat/rest/credential-resource rather than on https://www.twilio.com/docs
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- PASSPaths robots.txt points at answerthe 6 concrete paths your robots.txt allows all answer
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 13 advertised grants, so an unattended agent has a documented path to a token
- FAILMCP surfaceMCP mentioned 3x in your own files, but nothing answered at mcp.twilio.com, mcp.twilio.com/mcp, mcp.twilio.com/v1/mcp, api.twilio.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://twilio.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://twilio.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- PASSProgrammatic key provisioning2 of 7 provisioning phrases across the 6 documents we read: "provisioning api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://twilio.com/pricing: "no credit card", "free trial"
E · Integration
- PASSTyped SDK on the registrytwilio@6.1.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://www.twilio.com/docs/authy/twilioauth-sdk/quickstart/obtaining-authy-api-key
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for twilio.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.