ExxonMobil: 71 of 100 on Ora's agent-readiness scan

The score

ExxonMobil is an oil and gas company based in Texas, one of the largest in the world by revenue.

• 71of 100, grade B
  Ora's agent-readiness scan of exxonmobil.com, read 9 November 2026.
• 11Discovery, of 16
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 32Access, of 40
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 34Usability, of 52
  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.

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

Ora's one-line summary: ExxonMobil developer portal offers API documentation, but lacks declared OAuth scopes for secure 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. Scoped permissions, worth about 4.3 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
2. Public API with reachable endpoints, worth about 3.4 points by Ora's estimate: API described in documentation at https://developer.exxonmobil.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.
3. Developer resource discoverability, worth about 2.8 points by Ora's estimate: Agent struggled to find developer resources by name - only 1 result(s) out of 10. Found on site but absent from this search sample: developer portal, MCP server.

Our read

ExxonMobil is a B, and the surprise is where it comes from. All four agent user agents reach exxonmobil.com, robots.txt allows the search and training crawlers, the sitemap index is valid and the metadata is complete, and the home page gives 2,343 characters with an H1 whose heading tree skips from H2 to H4; the JSON-LD block carries no identity type, and a bot shield answered the llms.txt and markdown probes with 403, which Ora does not count against the site. The Access layer reads 32 of 40. The act layer is what lifts an oil company above most banks and retailers here: an MCP server at support.exxonmobil.com/mcp that answers and requires authentication, OAuth authorization server metadata beside it, and developer.exxonmobil.com with documentation, though the API has no machine-verifiable surface and Ora found no declared scopes, no SDK and no CLI, so the Usability layer reads 34 of 52. Declared OAuth scopes are the fix Ora values most, about 4.3 points; the server they would describe is already running.

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