PepsiCo: 44 of 100 on Ora's agent-readiness scan

The score

PepsiCo is a food and beverage company based in New York, the maker of Pepsi, Lay's and Quaker.

• 44of 100, grade D
  Ora's agent-readiness scan of pepsico.com, read 9 November 2026.
• 10Discovery, of 14
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 25Access, of 56
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 12Usability, of 40
  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: PepsiCo maintains strong brand discoverability and search presence, but lacks a publicly reachable API surface for agent integration.

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. Public API with reachable endpoints, worth about 7.8 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
2. MCP server / manifest, worth about 6.7 points by Ora's estimate: No MCP server or manifest found.
3. WebMCP support, worth about 5.6 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 13 same-origin script bundle(s) for modelContext registrations).

Our read

PepsiCo opens the door onto 510 characters. All four agent user agents get in, robots.txt allows the crawlers, five of five sampled pages read and the sitemap lists 2,548 pages, but the home page gives 510 characters at a 1 percent text ratio, there is no JSON-LD and no llms.txt, and the metadata lacks og:type, so the Access layer reads 25 of 56. The act layer is empty in the way a food company's usually is, with one twist: the link Ora read as developer documentation is a PDF about modern slavery and human trafficking under /docs, so the portal row is a filing cabinet. There is no public API, no OpenAPI specification, and neither an MCP server nor OAuth discovery, so the Usability layer reads 12 of 40. A home page that says more than 510 characters and an Organization block are the two rows for this quarter; whether a snack company wants an API is a different meeting.

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