Verizon: 48 of 100 on Ora's agent-readiness scan

The score

Verizon is a telecommunications company based in New York.

• 48of 100, grade C
  Ora's agent-readiness scan of verizon.com, read 9 November 2026.
• 9Discovery, of 15
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 33Access, of 58
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 17Usability, of 47
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44.

Ora's one-line summary: Verizon has SDK packages and developer documentation, but lacks OpenAPI specification and OAuth 2.0 support.

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.

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.

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.

1. MCP server / manifest, worth about 5.7 points by Ora's estimate: No MCP server or manifest found.
2. OAuth 2.0 support, worth about 4.7 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.
3. Scoped permissions, worth about 4.7 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.

Our read

Verizon lets every agent in and has built half of what they would need. All four agent user agents reach verizon.com, robots.txt allows the search and training crawlers, five of five sampled pages read with substantive text, the sitemap index is valid and an llms.txt sits at developers.verizon.com, so the Access layer reads 33 of 58; the home page gives 1,556 characters without an H1, there is no JSON-LD and the metadata lacks og:image. The act layer is developers.verizon.com, a real portal with documentation and SDKs on npm and RubyGems, whose API has no machine-verifiable surface; Ora found no OpenAPI specification, no OAuth or OpenID Connect discovery and no MCP server, so the Usability layer reads 17 of 47. The Discovery layer is 9 of 15: verizon.com was not in the top ten for its wireless carrier term. An MCP server is the fix Ora values most, at 5.7 points; an Organization block is the one the web team can ship this week.

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 verizon.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.