# AT&T scores 41 out of 100 on the Agent Readiness Index

AT&T reaches level 2, Legible. Web experience is the strongest area at 100 out of 100. Protocol access is the weakest at 0.

AT&T was scanned on October 2, 2026. Its score is 41 out of 100, level 2, Legible. An agent can read and cite your content. To reach level 3, Connectable: Offer a programmatic path: a live MCP server, a data sharing program with OAuth metadata, or a verified Poppy file.

Website: [att.com](https://www.att.com)

## Score by area

| Area | Score | What it asks |
| --- | --- | --- |
| Discoverability | 93 out of 100, worth 15 points | Can an agent find and read your pages? |
| Protocol access | 0 out of 100, worth 20 points | Can an agent connect to you through MCP or an API? |
| Identity and delegation | 0 out of 100, worth 20 points | Can a customer give an agent limited access without sharing a password? |
| Web experience | 100 out of 100, worth 15 points | Does your site work when an agent uses it? |
| Voice and IVR | Not measured yet | What happens when an agent calls your phone line? |
| Policy and governance | 36 out of 100, worth 10 points | Do your terms allow agents that act for customers? |

## What is holding AT&T back

1. **MCP server**, 8 points lost. No MCP server, server card or registry entry was found for this organization. Fix: Publish a remote MCP server with OAuth. Start with read only tools such as account status, orders or location search, and publish a server card at /.well known/mcp/server card.
2. **OAuth and OpenID metadata**, 5 points lost. No OAuth or OpenID metadata was found on the 10 hosts that answered. 7 other hosts did not answer the scanner and could not be checked. Agents cannot discover where to send a customer to approve access. Fix: Publish /.well known/oauth authorization server and /.well known/oauth protected resource for the customer facing APIs.
3. **Developer and data sharing program**, 4 points lost. No developer portal or data sharing program was found on public pages. Fix: Document the program, the standard in use for example FDX in US banking, the supported partners and a sandbox.
4. **PKCE and client registration**, 4 points lost. No authorization server metadata, so PKCE and client registration could not be confirmed. Fix: Require PKCE with S256 and support client ID metadata documents or dynamic client registration for approved agent clients.

## What already works

- Sign in page loads for a declared agent in a browser
- Sign in form structure and autofill hints
- llms.txt guide for agents

## How AT&T compares

Ranked 9 of 12 on the [Telecom and internet leaderboard](https://readyindex.ai/leaderboard_telecom). The average score for telecom and internet is 45.2 out of 100 across 34 organizations. The average across all 1,421 scored organizations is 42.2 out of 100.

## Similar organizations

- [Frontier](https://readyindex.ai/frontier_com), 44 out of 100
- [Orange](https://readyindex.ai/orange_com), 43 out of 100
- [Telstra](https://readyindex.ai/telstra_com_au), 43 out of 100
- [Boost Mobile](https://readyindex.ai/boostmobile_com), 41 out of 100
- [Lumen Technologies](https://readyindex.ai/lumen_com), 41 out of 100
- [Ting](https://readyindex.ai/ting_com), 39 out of 100

## More on this report

- [This report as markdown](https://readyindex.ai/att_com.md)
- [This report as JSON data](https://readyindex.ai/api/reports/att_com)
- [How the score is worked out](https://readyindex.ai/method)
- [All leaderboards](https://readyindex.ai/leaderboards)
- [Every scored organization](https://readyindex.ai/organizations)
- [Scan your own website](https://readyindex.ai/)

---
Source: https://readyindex.ai/att_com
Updated: 2026-10-02
From the Agent Readiness Index by Encore AI. When you quote a score, please link to the report it came from.