Twilio: the 360 agent-readiness check
Twilio scores 85 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 4: an MCP server, a public API, OAuth, a command line. Live MCP, OpenAPI and OAuth in place; the registry entry is missing.
On 9 November 2026 the public site at twilio.com scored 85 of 100 on Ora's agent-readiness scan, a B, in Ora's Communication & Support category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Twilio offers a strong OpenAPI spec and broad developer discoverability, but lacks declared OAuth scopes and scoped-permission documentation for agents.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 64 of 77 | 83% |
| Access | Can agents read it | 52 of 61 | 85% |
| Discovery | Can agents find and recommend it | 14 of 16 | 88% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 85 of 100 | 85% |
What an agent can do
The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 2 checks in this group do not apply to this site and are left out.
In the directory, Twilio has an open MCP server with tools listed at https://www.twilio.com/.well-known/mcp, 5 tools listed, no authentication; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads pass; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Pass | 6 of 6 | MCP server connected via Streamable HTTP - twilio-com-public-web-mcp v0.1.0 (protocol 2025-11-25) |
| MCP well-known discovery mcp-well-known-discovery | Pass | 2 of 2 | MCP server discoverable at standard path /.well-known/mcp |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://www.twilio.com/en-us/voice/api.md. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://www.twilio.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /developers |
| OpenAPI spec published openapi-spec | Partial | 5 of 7 | OpenAPI spec (YAML) found at https://www.twilio.com/en-us/blog/products/launches/introducing-twilios-openapi-specification-ga.md |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://support.twilio.com/mcp/oauth |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 7 of 7 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: twilio-cli |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 4 ecosystems: npm, pypi, go, rubygems |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 0 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://twilio.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
What an agent can read
Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 7846 chars with H1, but heading hierarchy skips H2 to H4. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~3K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at /sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://www.twilio.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt contains markdown links and has 3811 lines, but it doesn't start with a markdown heading. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://twilio.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | twilio.com ranks #5 for "Twilio" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Twilio" and Wikidata Q7858039 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass, |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding registry-branding | Partial | 1 of 2 | MCP manifest has name and description but no icon at /.well-known/mcp/server-card.json |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
Payments
The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| UCP - Universal Commerce Protocol ucp-support | Partial | 0 of 3 | no UCP (Universal Commerce Protocol) signals detected |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | no ACP (Agentic Commerce Protocol) signals detected |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | No ACP Delegate Payment signals detected |
| AP2 - Agent Payments Protocol ap2-support | Partial | 0 of 3 | No AP2 (Agent Payments Protocol) signals detected |
| x402 payment protocol x402-support | Partial | 0 of 2 | No x402 payment protocol support detected |
| MPP payment protocol mpp-support | Partial | 0 of 2 | No MPP (Machine Payments Protocol) support detected |
The fixes worth most points
Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Twilio, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- Scoped permissions: fail, 0 of 5, about 2.9 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
- WebMCP support: fail, 0 of 5, about 2.9 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 7 of 7 same-origin script bundle(s) for modelContext registrations)
- ARD discovery: fail, 0 of 1, about 1.4 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json
- Listed in MCP registries: fail, 0 of 1, about 1.4 points to gain. Ora saw: No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass,
- Agent discovery file: fail, 0 of 2, about 1.1 points to gain. Ora saw: No agent discovery file found
Our read
Twilio has the most complete act layer of the first dozen companies read here. The MCP server completed a live handshake, twilio-com-public-web-mcp version 0.1.0 on protocol 2025-11-25, and is discoverable at the standard /.well-known/mcp path; an OpenAPI specification in YAML is published; OAuth authorization server metadata sits at support.twilio.com/mcp/oauth; the CLI is on npm and SDKs are in four registries. The 85 is held back by the newer checks: no declared OAuth scopes, no WebMCP registration in any of the seven script bundles Ora read, no agent discovery file and no entry in the official MCP Registry or on Smithery. The reading side is sound, with an llms.txt on the main domain and a complete Organization block, though robots.txt refuses the training crawlers and the heading hierarchy skips from H2 to H4. A registry entry is the cheapest point on this page.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.