--- title: "ExxonMobil: 71 of 100 on Ora's scan | Am I Ready for Agents?" description: "ExxonMobil scores 71 of 100 on Ora's agent-readiness scan, grade B, read 9 Nov 2026. An oil company with a live MCP server at its support desk, and a B." canonical: https://amireadyforagents.com/blog/exxonmobil-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # ExxonMobil: 71 of 100 on Ora's scan | Am I Ready for Agents? > ExxonMobil scores 71 of 100 on Ora's agent-readiness scan, grade B, read 9 Nov 2026. An oil company with a live MCP server at its support desk, and a B. Source: https://amireadyforagents.com/blog/exxonmobil-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # ExxonMobil: 71 of 100 on Ora's agent-readiness scan ## In short ExxonMobil scores 71 of 100 on Ora's agent-readiness scan, grade B, read on 9 November 2026. 93 percent of the 132,085 domains Ora ranks score under 70, and the average score is 44. An oil company with a live MCP server at its support desk, and a B. ## 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. | Check | Result | What Ora saw | | --- | --- | --- | | Not blocked by bot detection | Pass, 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). | | Agent crawler reachability | Pass, 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable | | robots.txt AI crawler policy | Pass, 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. | | robots.txt agent-user policy | Pass, 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://exxonmobil.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | 2343 chars with H1, but first content heading is H4, not H1; heading hierarchy skips H2 to H4 | | Homepage not hidden from search | Pass, 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. | ## 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 | Did not apply, 0 of 1 | Can't verify: a bot shield answered our request to exxonmobil.com/.well-known/llms.txt (HTTP 403); developer.exxonmobil.com/llms.txt (HTTP 403); | | llms.txt formatting | Did not apply, 0 of 2 | Can't verify: a bot shield answered our request to developer.exxonmobil.com/.well-known/llms.txt (HTTP 403) instead of the site. That is not counted against the site. | | 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 | Can't verify: a bot shield answered our request to developer.exxonmobil.com/ (HTTP 403); exxonmobil.com/ (HTTP 403) instead of the site. That is not counted against the site. | | JSON-LD structured data | Partial, 1 of 4 | JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is | | Organization schema completeness | Fail, 0 of 2 | No Organization type found in JSON-LD | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.exxonmobil.com/sitemap.xml with multiple sitemaps entries | | Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type | | Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Partial, 5 of 6 | MCP server detected at https://support.exxonmobil.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. | | MCP well-known discovery | Partial, 1 of 2 | MCP server at https://support.exxonmobil.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it | | Public API with reachable endpoints | Partial, 3 of 7 | API described in documentation at https://developer.exxonmobil.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. | | Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developer.exxonmobil.com | | OpenAPI spec published | Did not apply, 0 of 7 | Can't verify: a bot shield answered our request to developer.exxonmobil.com/openapi (HTTP 403) instead of the site. That is not counted against the site. | | Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developer.exxonmobil.com | | OAuth 2.0 support | Pass, 5 of 5 | OAuth authorization server metadata at https://support.exxonmobil.com/mcp/oauth | | 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 | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to exxonmobil.com/docs (HTTP 403); exxonmobil.com/docs/api (HTTP 403); exxonmobil.com/developers (HTTP 403), and 1 more instead of the site. | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "ExxonMobil" and Wikidata Q156238 both verified - domain confirmed on both sources | | Brand name discoverability | Pass, 3 of 3 | exxonmobil.com ranks #2 for "ExxonMobil energy company" | | 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 | Partial, 1 of 3 | 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. | 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](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check). 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 Ora](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check)The same checks, the same scoring, on your own site. - [The self-check, 18 questions](https://amireadyforagents.com/self-check)What to ask for, in business terms, before the scan. - [All the 360 checks](https://amireadyforagents.com/blog)The other companies in this series, newest first. ## Sources 1. [Ora report for exxonmobil.com](https://ora.ai/score/exxonmobil.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/exxonmobil.com), read 9 Nov 2026. Vendor claim. Last reviewed 9 November 2026 Reviewed 9 November 2026. [1 source](#sources), each with the day it was read.