---
title: "Hertz: the 360 agent-readiness check | Agent Ready Checkout"
description: "Hertz on Ora's agent-readiness scan, read 2026-11-14: 59 of 100, grade C. The pay layer did not apply. Every layer, the fixes worth most and the editors' read."
canonical: https://agentreadycheckout.com/blog/hertz-agent-readiness
site: "Agent Ready Checkout"
last_updated: 2026-11-14
date: 2026-11-09
section: "360 checks"
---

# Hertz: the 360 agent-readiness check | Agent Ready Checkout

> Hertz on Ora's agent-readiness scan, read 2026-11-14: 59 of 100, grade C. The pay layer did not apply. Every layer, the fixes worth most and the editors' read.

Source: https://agentreadycheckout.com/blog/hertz-agent-readiness
Site: Agent Ready Checkout
Last reviewed: 2026-11-14

360 check, 9 Nov 2026

# Hertz on the pay layer: the 360 agent-readiness check

In short

Hertz scores 59 of 100 on Ora's agent-readiness scan, a C, read 14 Nov 2026. The six payment checks did not apply to hertz.com on this read, which is how Ora treats a site it does not read as a shop. A score of 59 on a home page of 59 characters.

On 14 Nov 2026 the public site at hertz.com scored **59 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycheckout.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C. Hertz is the car rental company with a fleet in more than 160 countries, so this check reads the Payments layer first: the six checks that look for x402, MPP, UCP, ACP and AP2 on the domain, the same protocols this site's matrix tracks row by row. The other layers follow, with every check Ora ran and what it saw. Ora's one-line summary: Hertz provides strong brand discoverability and sitemaps, but requires JavaScript rendering for page content.

## The score

| Layer | Points | Share | What the layer asks |
| --- | --- | --- | --- |
| Discovery | 10 of 11 | 91% | Can agents find and recommend it |
| Access | 16 of 40 | 40% | Can agents read it |
| Usability | 8 of 14 | 57% | Can agents use it |
| Payments | 0 of 0 | none apply | Can agents pay |
|  |
| Total | 59 of 100 | 59% | Grade C |

## The pay layer

Ora did not run the six payment checks against hertz.com on this read: it marks them not applicable on a site it does not read as a shop, so the layer has no maximum and costs nothing. A travel seller that sells online can still publish any of the five protocols; the matrix says which processors and platforms carry each one. Each protocol links to its matrix row, where the processors and platforms that carry it are dated and sourced.

| Payment check | Result | Points | Matrix row | What Ora saw |
| --- | --- | --- | --- | --- |
| x402 | Does not apply | 0 of 2 | x402 in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| MPP | Does not apply | 0 of 2 | MPP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| UCP | Does not apply | 0 of 3 | UCP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP delegate payment | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| AP2 | Does not apply | 0 of 3 | AP2 in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |

## The other layers, check by check

Every check Ora ran on hertz.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.

### Discovery: 10 of 11

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
| Brand name discoverability | Pass | 3 of 3 | hertz.com ranks #2 for "Car Rental" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Hertz Global Holdings" and Wikidata Q1543874 both verified - domain confirmed on both sources |
| 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. |
| Agent platform configs | Fail | 0 of 1 | Could not locate a public repo containing agent configs or rules. If our probes missed it, AI coding agents likely will too - link the repo from your homepage or docs so it's discoverable. |
| Agent Plugins manifest | Fail | 0 of 1 | No Agent Plugins manifest (plugin.json) found in discovered repos |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| 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. |

### Access: 16 of 40

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.hertz.com/hertz-sitemap.xml with 212 entries |
| Content without JavaScript | Fail | 0 of 3 | Homepage: Very little text content (59 chars) - likely JS-rendered, invisible to AI crawlers. Sampled pages with almost no text without JavaScript (4 of 4): https://www.hertz.com/p/collections/dream (59 chars) |
| Not blocked by bot detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (20 community skills with potential relation to this domain found, but only self-published official skills count) |
| pricing.md exists | Fail | 0 of 2 | No pricing.md found - agents need machine-readable pricing to compare products and make purchase recommendations |
| NLWeb Schema Feeds | Fail | 0 of 1 | No schemamap: directive in robots.txt |
| MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| HTTP Link headers (RFC 8288) | Fail | 0 of 1 | No HTTP Link response headers (RFC 8288) found |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://hertz.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Modular llms.txt per product area | Fail | 0 of 1 | No section-level llms.txt found. Tried /docs/llms.txt, /api/llms.txt, /developers/llms.txt, /guides/llms.txt, /reference/llms.txt. This is a bonus check: it can add a point and never costs one. |
| Sitemap freshness (lastmod) | Partial | 0 of 1 | Sitemap lastmod dates are all stale - the newest is 2109 days old. Update lastmod when content changes or agents will deprioritize the whole site as unmaintained. |
| 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://hertz.com/. Declared policy only |
| 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 |
| 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 |
| Pricing info accessible | Fail | 0 of 3 | No pricing page or pricing data found |
| Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |
| Skills.sh skill quality | Fail | 0 of 2 | No official skills on skills.sh to evaluate |
| JSON-LD entity linking (sameAs) | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Metadata completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en-US", og:image, og:type |
| Organization schema completeness | Fail | 0 of 2 | No Organization type found in JSON-LD |
| Schema type breadth | Partial | 1 of 2 | Some extended schema types found: BreadcrumbList - add 2 more types that match what the homepage shows, for full coverage |
| Trust anchor pages | Fail | 0 of 2 | No trust anchor pages found with sufficient content (About, Contact, Privacy) |
| Markdown alternate link | Fail | 0 of 1 | No sampled page advertises a markdown alternate. Add <link rel="alternate" type="text/markdown" href="..."> (or the equivalent Link response header) pointing at a markdown twin of the page. |
| Redirect hygiene | Pass | 1 of 1 | Pass, no detail recorded. |
| Page token budget | Pass | 1 of 1 | All 5 measured pages fit an agent context budget (largest ~1K tokens) |
| Content behind auth | Pass | 2 of 2 | All 5 sampled pages are publicly readable (0 with substantive content) |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| 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 |
| Markdown content negotiation (acceptmarkdown.com) | Fail | 0 of 1 | Homepage https://hertz.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html;charset=utf-8; Vary header missing Accept (got "none") |
| Bot-UA markdown serving | Fail | 0 of 1 | No 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. |
| Agent crawler reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |

### Usability: 8 of 14

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| OAuth 2.0 support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://auth.hertz.com |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| auth.md structure | Fail | 0 of 2 | No /auth.md found at site root |
| Agent auth discovery metadata | Fail | 0 of 3 | Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: hertz.com, api.hertz.com. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://hertz.com/api, https://hertz.com/api/v1, https://hertz.com/v1, https://hertz.com/v2, https://hertz.com/agent/identity, https://hertz.com/agent/auth |
| agent_auth endpoints reachable | Fail | 0 of 2 | No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 5 of 5 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| NLWeb streaming support | Fail | 0 of 1 | NLWeb /ask does not support SSE streaming via GET or POST |
| MCP server-card.json | Fail | 0 of 2 | No MCP server card found (checked /.well-known/mcp/server-card.json, the site's ai-catalog.json, servers[].card in mcp.json, and <server>/server-card) |
| Product + docs MCP coverage | Fail | 0 of 2 | This bonus needs two MCP servers: one for your product so agents can take actions, and a separate one for your documentation so agents can answer questions from your docs. |
| Sandbox / test environment | Fail | 0 of 2 | No sandbox or test environment found |
| Agent-friendly 404s | Partial | 1 of 2 | The nonexistent path https://hertz.com/__ora-404-probe-i1euvre1 correctly returns HTTP 404. Partial credit: no Markdown error body was detected. |
| Accessibility-tree injection safety (bonus) | Pass | 2 of 2 | Pass, no detail recorded. |

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Hertz.

WebMCP support

Fail, 0 of 5, about 15.9 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 5 of 5 same-origin script bundle(s) for modelContext registrations).

Agent auth discovery metadata

Fail, 0 of 3, about 3.4 points to gain. Ora saw: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: hertz.com, api.hertz.com.

Agent-friendly 404s

Partial, 1 of 2, about 3.2 points to gain. Ora saw: The nonexistent path https://hertz.com/\_\_ora-404-probe-i1euvre1 correctly returns HTTP 404. Partial credit: no Markdown error body was detected.

Agent instruction / when-to-use

Fail, 0 of 3, about 2.5 points to gain. Ora saw: No agent instruction file with when-to-use guidance found.

Content without JavaScript

Fail, 0 of 3, about 2.5 points to gain. Ora saw: Homepage: Very little text content (59 chars) - likely JS-rendered, invisible to AI crawlers. Sampled pages with almost no text without JavaScript (4 of 4): https://www.hertz.com/p/collections/dream (59 chars).

## Our read

Hertz scores 59 with a home page of 59 characters, and both numbers have the same cause: the site publishes neither an API nor a developer portal, and no MCP server, so the Usability layer has a maximum of 14 and the rows that fail elsewhere are not counted. The door is open to all four agent user agents, robots.txt allows the search and training crawlers and the sitemap carries 212 entries; the page is rendered by JavaScript, with one JSON-LD block that lacks an identity type and no llms.txt. Ora read no commerce signals on one of the largest car rental companies in the world, so the six payment checks did not apply on this read. The act layer is OpenID Connect discovery at auth.hertz.com and nothing else; the WebMCP estimate of 15.9 points is large because so few checks apply. hertz.com ranks second for Car Rental. A rental is the booking an agent makes after the flight, and the page it lands on is 59 characters.

## Test your own checkout

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadycheckout.com&utm_medium=referral&utm_campaign=check) and read the same layers for your own site, with the six payment checks mapped to this matrix on [the Ora Payments page](https://agentreadycheckout.com/method/ora-payments-layer). The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy. [Why Ora, and its limits](https://agentreadycheckout.com/guides/best-ai-readiness-tools-2026).

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentreadycheckout.com/blog), one company a day. Corrections to [the corrections page](https://agentreadycheckout.com/corrections).

## Sources

1.  [ora.ai/api/score/hertz.com, Ora's scan (vendor)](https://ora.ai/api/score/hertz.com?utm_source=agentreadycheckout.com&utm_medium=referral&utm_campaign=check), read 14 Nov 2026
2.  [Ora check catalog (GET /api/checks)](https://ora.ai/api/checks?utm_source=agentreadycheckout.com&utm_medium=referral&utm_campaign=check), read 14 Nov 2026
3.  [hertz.com, the company's site](https://www.hertz.com/us/en), read 14 Nov 2026

Last reviewed 14 Nov 2026

## Edition

Matrix edition of 4 Nov 2026.

Reviewed 14 Nov 2026, [3 sources](#sources-h).

## Method

Every number on this page is read from Ora's score file for the domain on the date shown. The verdict is ours.

[Methodology](https://agentreadycheckout.com/method)