AT&T: 34 of 100 on Ora's agent-readiness scan
In short
AT&T scores 34 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. A challenge for every agent, in front of a developer portal that handles sign-in for people.
The score
AT&T is a telecommunications company based in Dallas.
- 34of 100, grade DOra's agent-readiness scan of att.com, read 9 November 2026.
- 6Discovery, of 10Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 12Access, of 50Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 17Usability, of 58Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.
Ora's one-line summary: ATT offers OAuth 2.0 and a public API with JSON responses, but lacks an OpenAPI specification for agent discovery.
What an assistant meets at the door
Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.
| Check | Result | What Ora saw |
|---|---|---|
| Not blocked by bot detection | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass. |
| Agent crawler reachability | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged). |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for search crawlers: WAF/bot challenge (HTTP 403) |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: WAF/bot challenge (HTTP 403) |
| Content without JavaScript | Partial, 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage blocked by WAF - cannot read its indexing directives |
What it can read, and what it can do
The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.
| Check | Result | What Ora saw |
|---|---|---|
| llms.txt exists | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | 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). |
| Bot-UA markdown serving | Did not apply, 0 of 1 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| JSON-LD structured data | Fail, 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness | Fail, 0 of 2 | No JSON-LD found - Organization schema missing |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| Metadata completeness | Partial, 1 of 2 | Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Pass, 7 of 7 | API described in documentation at https://developer.att.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://att.com/graphql is reachable; |
| Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developer.att.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developer.att.com |
| OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://auth.att.com |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Fail, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q35476 (AT&T) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Partial, 1 of 3 | att.com ranks #6 for "att" (searched your brand name alone: we could not read a product term from your site) |
| Category share of voice | Did not apply, 0 of 6 | Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name). |
| Developer resource discoverability | Pass, 3 of 3 | Agent discovered 1 developer-resource type by name (auth docs) across 1 page |
The six payment checks did not apply on this read: Ora did not read the site as a shop.
Three fixes to hand to the web team
Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.
- OpenAPI spec published, worth about 4.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
- MCP server / manifest, worth about 4.6 points by Ora's estimate: No MCP server or manifest found.
- Brand name discoverability, worth about 4.4 points by Ora's estimate: att.com ranks #6 for "att" (searched your brand name alone: we could not read a product term from your site).
Our read
AT&T answers every agent with a challenge. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot, robots.txt came back as a 403 challenge and the home page as a security page, so the door, content, policy and structured-data rows are unverified rather than failed, and the Access layer reads 12 of 50 with only one of four metadata signals in view. The act layer is better than the door suggests: developer.att.com is a real portal with documentation, and OpenID Connect discovery sits at auth.att.com; the API it describes has no machine-verifiable surface, and Ora found neither an OpenAPI specification nor an MCP server, and no SDK in any registry, so the Usability layer reads 17 of 58. The domain ranks sixth for att, a search that ran on the bare name because the probe could not read a product term from the site. A carrier that sells connectivity has a corporate site no agent can connect to; the door is the first row to fix.
Test your own site
Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for att.com; a scan of a public site takes a few minutes and needs no account.
- Scan your domain on OraThe same checks, the same scoring, on your own site.
- The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
- All the 360 checksThe other companies in this series, newest first.
Sources
- Ora report for att.com (ora.ai/score/att.com), read 9 Nov 2026. Vendor claim.
Last reviewed