Valero Energy: 62 of 100 on Ora's agent-readiness scan

In short

Valero Energy scores 62 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. Readable to every agent, with no JSON-LD and two Open Graph tags missing.

The score

Valero Energy is a refiner based in San Antonio.

  • 62of 100, grade C
    Ora's agent-readiness scan of valero.com, read 9 November 2026.
  • 8Discovery, of 11
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 19Access, of 41
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 13Usability, of 19
    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.

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

Ora's one-line summary: Valero offers a sound web presence and crawler-friendly setup, but lacks WebMCP support and JSON-LD structured data for agents.

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.

The door at valero.com
CheckResultWhat Ora saw
Not blocked by bot detectionPass, 2 of 2Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
Agent crawler reachabilityPass, 2 of 2Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable
robots.txt AI crawler policyPass, 2 of 2AI 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 policyPass, 2 of 2No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://valero.com/. Declared policy only;
Content without JavaScriptPass, 3 of 3Homepage: 1466 chars, semantic headings (1 H1 + 5 H2s + 5 H3s), 7.6% content ratio. 5 of 5 sampled inner pages have text without JavaScript.
Homepage not hidden from searchPass, 1 of 1No 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.

Reading valero.com
CheckResultWhat Ora saw
llms.txt existsFail, 0 of 1No llms.txt found at /llms.txt or /.well-known/llms.txt.
llms.txt formattingFail, 0 of 2No llms.txt found to evaluate quality
Markdown agent docsFail, 0 of 1Missing 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 servingFail, 0 of 1No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly.
JSON-LD structured dataFail, 0 of 4No JSON-LD structured data found on homepage
Organization schema completenessFail, 0 of 2No JSON-LD found - Organization schema missing
Sitemap existsPass, 2 of 2Valid sitemap found at https://www.valero.com/sitemap.xml with 144 entries
Metadata completenessPartial, 1 of 22/4 metadata signals present - missing: og:image, og:type
Page token budgetPass, 1 of 1All 6 measured pages fit an agent context budget (largest ~2K tokens)
Acting through valero.com
CheckResultWhat Ora saw
MCP server / manifestDid not apply, 0 of 6No MCP server or manifest found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsDid not apply, 0 of 7No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
Public API/docs linked from homepageDid not apply, 0 of 3No public API or documentation page linked from homepage
OpenAPI spec publishedDid not apply, 0 of 7No OpenAPI/Swagger specification found
Developer portalDid not apply, 0 of 6No developer portal found
OAuth 2.0 supportDid not apply, 0 of 5No OAuth 2.0 or OpenID Connect support detected
Scoped permissionsDid not apply, 0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
Multi-language SDK packagesDid not apply, 0 of 3No SDK packages found across language ecosystems
CLI tool availableDid not apply, 0 of 3No CLI tool found
WebMCP supportFail, 0 of 5No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 3 of 3 same-origin script bundle(s) for modelContext registrations)
Finding Valero Energy
CheckResultWhat Ora saw
Wikipedia / Wikidata entity presencePass, 4 of 4Wikipedia "Valero Energy" and Wikidata Q1283291 both verified - domain confirmed on both sources
Brand name discoverabilityPartial, 1 of 3valero.com ranks #6 for "Valero" (searched your brand name alone: no main product term from your homepage qualified)
Category share of voiceDid not apply, 0 of 6Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name).
Developer resource discoverabilityDid not apply, 0 of 3In a search for your API docs, none of the 10 results is your official docs

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. WebMCP support, worth about 11.7 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 3 of 3 same-origin script bundle(s) for modelContext registrations).
  2. Brand name discoverability, worth about 4 points by Ora's estimate: valero.com ranks #6 for "Valero" (searched your brand name alone: no main product term from your homepage qualified).
  3. JSON-LD structured data, worth about 3.3 points by Ora's estimate: No JSON-LD structured data found on homepage.

Our read

Valero opens to every agent Ora tested and shows them a tidy page: 1,466 characters without JavaScript at a 7.6 percent content ratio, five of five inner pages readable, a 144-entry sitemap, a correct 404 and a robots.txt that allows the AI crawlers and restricts none of the user-triggered agents. What the page lacks is the layer that tells an agent what it is reading: there is no JSON-LD at all, so the Organization row is empty, and metadata sits at 2 of 4 with og:image and og:type missing. The act layer is empty by design, with no public API, developer portal, MCP server or OAuth, so the Usability layer reads 13 of 19 and WebMCP tops the fix list at 11.7 points. Discovery is 8 of 11, with both Wikipedia and Wikidata confirming the domain. An Organization block and the two missing Open Graph tags are the cheapest rows on this page, and together they would tell an agent whose site it has just read.

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 valero.com; a scan of a public site takes a few minutes and needs no account.

Sources

  1. Ora report for valero.com (ora.ai/score/valero.com), read 9 Nov 2026. Vendor claim.

Last reviewed