Chevron: 18 of 100 on Ora's agent-readiness scan
In short
Chevron scores 18 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44. Six agents blocked, a 403 at robots.txt and an Access layer of 0 of 41.
The score
Chevron is an oil and gas company based in Texas, formerly in California.
- 18of 100, grade FOra's agent-readiness scan of chevron.com, read 9 November 2026.
- 3Discovery, of 9Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 0Access, of 41Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 11Usability, of 47Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44.
Ora's one-line summary: Chevron.com offers a public API with reachable endpoints, but lacks an OpenAPI specification.
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 | Fail, 0 of 2 | Agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended |
| Agent crawler reachability | Fail, 0 of 2 | No major AI crawler can reach the homepage - ChatGPT-User: blocked, ClaudeBot: blocked, Google-Extended: blocked, ora-agent: blocked, DeepSeekBot: blocked |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for training and search crawlers: HTTP 403 |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: HTTP 403 |
| Content without JavaScript | error, 0 of 3 | Could not fetch homepage |
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 | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| 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 | Fail, 0 of 1 | No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. |
| JSON-LD structured data | error, 0 of 4 | Could not fetch homepage |
| Organization schema completeness | error, 0 of 2 | Could not fetch homepage |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| Metadata completeness | error, 0 of 2 | Could not fetch homepage |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Pass, 7 of 7 | GraphQL endpoint at https://chevron.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage | Fail, 0 of 3 | No public API or documentation page linked from homepage |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Did not apply, 0 of 6 | No developer portal found |
| OAuth 2.0 support | Did not apply, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Did not apply, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Pass, 3 of 3 | CLI tool found on npm: chevron |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q319642 (Chevron Corporation) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Partial, 1 of 3 | chevron.com appears once in brand-name search results for "chevron" (position #6 out of 7) |
| 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 | Fail, 0 of 3 | Agent searched for "chevron" developer resources but found nothing relevant |
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.
- Developer resource discoverability, worth about 7.4 points by Ora's estimate: Agent searched for "chevron" developer resources but found nothing relevant.
- MCP server / manifest, worth about 5.7 points by Ora's estimate: No MCP server or manifest found.
- OpenAPI spec published, worth about 5.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
Our read
Chevron blocks the agents outright. GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended and Applebot-Extended were all blocked at the door, robots.txt answered 403, and the home page could not be fetched, so the content, policy and structured-data rows are unverified rather than failed and the Access layer reads 0 of 41, the lowest in this series. There is no sitemap and no llms.txt. What Ora could reach is a GraphQL endpoint at chevron.com/graphql with introspection gated behind authentication, and a CLI package on npm named chevron, which may or may not be the oil company's; there is no developer portal, no OpenAPI specification and no MCP server, so the Usability layer reads 11 of 47. The domain appears once, in sixth place of seven, in a search for its own name, and Ora confirmed the Wikidata item without a Wikipedia match. An F that begins with a block is a decision, and the only row that changes anything is the first one.
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 chevron.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.
Sources
- Ora report for chevron.com (ora.ai/score/chevron.com), read 9 Nov 2026. Vendor claim.
Last reviewed