What does the agent readiness check test?

Real protocol probes of .well-known files (openapi.json, mcp.json, ai-plugin.json, security.txt), a live MCP initialize handshake, A2A agent-card validation, a 20-user-agent crawler audit, and a JS-parity check.

Is united.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-09 · log in to re-run

14%

Readiness

1/7

Verified (readable)

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

0/20 AI crawlers reached the homepage20 blocked

Ranks above 31% of 127 sites checkedcorpus avg 24/100

Not agent-ready

united.com has 1 of 7 readable agent standards in place; missing Webmcp, A2a, Anp, Ucp, Ap2, Llms Txt. 2 could not be read because the site refused our request (Mcp, Openapi), so they are not counted.

Assessment

1 of 7 readable agent-readiness checks verified (2 could not be read: the site refused our request). See per-protocol drawers for evidence and fix-it files.

Per-protocol verdicts

Mcpcould not read /mcp (no response) - the site refused our request, so this is not a findingCould not read

Webmcpno navigator.modelContext.register, <script type="webmcp">, or <link rel="modelcontext"> in HTMLNot found

A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found

Anpno /.well-known/did.jsonNot found

Ucpno /.well-known/agentic-commerce.json (and platform is not a UCP-shipping host)Not found

Ap2no /.well-known/ap2.jsonNot found

Openapicould not read /api/openapi.json (no response) - the site refused our request, so this is not a findingCould not read

Llms Txtno /llms.txtNot found

WikidataWikidata entity Q174769 (United Airlines)Verified

.well-known files

.well-known/mcp.jsonnot found404

Mcp Well Known Altnot found404

/mcp endpointcould not read404

Ai Plugin Legacynot found404

.well-known/agent.jsonnot found404

.well-known/agent-card.jsonnot found404

Anp Didnot found404

Openapi Well Knownnot found404

Openapi Rootnot found404

Openapi Apicould not read404

Ucp Well Knownnot found404

Ap2 Well Knownnot found404

Llms Txtnot found404

Llms Full Txtnot found404

robots.txt4155 bytes200

sitemap.xml72157 bytes200

AI crawler audit

0 of 20 AI user-agents reached the homepage.

What this means for united.com

On united.com (Custom), 1 of 7 readable agent standards are in place: Wikidata. Missing: Webmcp, A2a, Anp, Ucp, Ap2, Llms Txt.

Without JavaScript, your brand name still appears in the raw HTML, so crawlers that do not run JS can read it (detected a vue-empty-app hydration shell).

united.com scores higher than 31% of the 127 sites checked here so far; the average readiness score is 24/100.

Make united.com agent-ready

Start with the highest-impact gap: Webmcp. Publish a working MCP endpoint at /.well-known/mcp.json (the initialize handshake must succeed, not just return 200), add an A2A agent card, and keep the crawler path clean.

Frequently asked questions

Are these real probes or AI guesses?

Real probes. We fetch the actual files, run a real MCP initialize handshake, and validate A2A cards against their schema. No model decides a verdict.

Does united.com need every standard to pass?

No. Start with the highest-impact gap above, then add the rest. Most sites win the most by shipping a working MCP endpoint and keeping the crawler path clean.

Check your own site free

Run the same protocol probes on any URL, then sign up free for the copy-paste fix-it files and the full 20-crawler audit.

Run a free check

Agent readiness on Custom

We have checked 64 other sites on Custom. The Custom hub aggregates protocol verification rates and average readiness scores across every Custom site checked here.

Is Custom ready for AI agents?