--- title: "Hyundai Motor: 44 of 100 on Ora's scan | Am I Ready for Agents?" description: "Hyundai Motor scores 44 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/hyundai-motor-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Hyundai Motor: 44 of 100 on Ora's scan | Am I Ready for Agents? > Hyundai Motor scores 44 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/hyundai-motor-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Hyundai Motor: 44 of 100 on Ora's agent-readiness scan ## In short Hyundai Motor scores 44 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. An MCP manifest that answers in invalid JSON, on a site the search engines miss. ## The score Hyundai Motor is a carmaker based in Seoul. - 44of 100, grade D Ora's agent-readiness scan of hyundai.com, read 9 November 2026. - 5Discovery, of 20 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 30Access, of 60 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 21Usability, of 44 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. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. Ora's one-line summary: Hyundai provides a developer documentation site, but lacks a discoverable 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 | Pass, 2 of 2 | Site accessible to 6 AI agent user-agents | | Agent crawler reachability | Pass, 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable | | robots.txt AI crawler policy | Pass, 1 of 2 | AI crawlers explicitly allowed (gptbot, oai-searchbot, claudebot, claude-searchbot, perplexitybot, google-extended) - consider blocking training-only crawlers (CCBot, ByteSpider) to earn full credit | | robots.txt agent-user policy | Pass, 2 of 2 | User-triggered agents explicitly allowed (chatgpt-user, claude-user) | | Content without JavaScript | Partial, 1 of 3 | Only 245 chars of text content, no H1 tag - agents see limited content | ## 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 | Pass, 1 of 1 | Found the llms.txt at https://developers.hyundai.com/llms.txt. | | llms.txt formatting | Pass, 2 of 2 | The llms.txt is well-formatted: 9 lines with markdown links, 285 characters in total. | | 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 | Fail, 0 of 4 | No JSON-LD structured data found on homepage | | Organization schema completeness | Fail, 0 of 2 | No JSON-LD found - Organization schema missing | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.hyundai.com/sitemap.xml with multiple sitemaps entries | | Metadata completeness | Partial, 1 of 2 | 3/4 metadata signals present - missing: og:type | | Page token budget | Pass, 1 of 1 | All 1 measured page fit an agent context budget (largest ~2K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Partial, 2 of 6 | MCP endpoint found at /.well-known/mcp/manifest.json but response is not valid JSON | | MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered | | Public API with reachable endpoints | Partial, 3 of 7 | Documentation site found at https://developers.hyundai.com but API content unclear. Best-of-protocols score: 3/7. | | Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developers.hyundai.com | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developers.hyundai.com | | OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://hyundai.com | | Scoped permissions | Did not apply, 0 of 5 | No scoped permissions or security schemes found | | Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems | | CLI tool available | Did not apply, 0 of 3 | No CLI tool found | | WebMCP support | Fail, 0 of 2 | 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 | Pass, 4 of 4 | Wikipedia "Hyundai Motor Company" and Wikidata Q55931 both verified - domain confirmed on both sources | | Brand name discoverability | Fail, 0 of 3 | "Hyundai USA" search returned 7 results but domain did not appear - brand may be too generic or not indexed | | 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 6 | Agent searched for "hyundai" 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. 1. Developer resource discoverability, worth about 6.7 points by Ora's estimate: Agent searched for "hyundai" developer resources but found nothing relevant. 2. JSON error responses, worth about 4 points by Ora's estimate: API does not return JSON error responses (or no API detected). 3. MCP Apps support, worth about 4 points by Ora's estimate: No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render. ## Our read Hyundai Motor has built more for agents than most carmakers and tells the search engines less. Six AI agent user agents reach hyundai.com, robots.txt explicitly allows GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot and names chatgpt-user and claude-user as permitted, an llms.txt sits at developers.hyundai.com, the sitemap index is valid, and developers.hyundai.com is a real portal with OpenID Connect discovery beside it; there is even an MCP manifest at /.well-known/mcp/manifest.json, which answers with something that is not valid JSON, so Ora scores it 2 of 6. Against that, the home page renders 245 characters without an H1, there is no JSON-LD, the API content is unclear and there is no OpenAPI specification, so the Access layer reads 30 of 60 and the Usability layer 21 of 44. The Discovery layer is 5 of 20: a search for Hyundai USA returned seven results without the domain, and a search for its developer resources found nothing. Fix the manifest's JSON and the carmaker has the first working MCP endpoint in this series. ## 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 hyundai.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 hyundai.com](https://ora.ai/score/hyundai.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/hyundai.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.