Hitachi: 15 of 100 on Ora's agent-readiness scan
In short
Hitachi scores 15 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. A home page that returned nothing and a Usability layer of 0 of 30.
The score
Hitachi is an industrial and digital conglomerate based in Tokyo.
- 15of 100, grade FOra's agent-readiness scan of hitachi.com, read 9 November 2026.
- 7Discovery, of 11Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 1Access, of 40Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 0Usability, of 30Whether 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: The site has no OpenAPI spec, no reachable public API, and no MCP server, leaving agents almost nothing to use.
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 | error, 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Did not apply, 0 of 2 | Can't verify crawler reachability. Our normal request could not read the homepage either, and a rate limit, server error, or timeout is not a block, so we can't tell if agents get in. |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for search crawlers: fetch unavailable |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: fetch unavailable |
| Content without JavaScript | Did not apply, 0 of 3 | Can't verify: our request for the homepage got no page back, so there is nothing to read without JavaScript. |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage not read - cannot tell whether it is hidden 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.
| 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 | error, 0 of 1 | Could not fetch with Accept: text/markdown |
| 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. |
| 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 | Fail, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| 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 | Did not apply, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Hitachi" and Wikidata Q53238 both verified - domain confirmed on both sources |
| Brand name discoverability | Pass, 3 of 3 | hitachi.com ranks #5 for "hitachi" (searched your brand name alone: we could not read a product term from your site) |
| 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 | In 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.
- Public API with reachable endpoints, worth about 10.4 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
- MCP server / manifest, worth about 8.9 points by Ora's estimate: No MCP server or manifest found.
- WebMCP support, worth about 7.4 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
Our read
Hitachi's 15 is a read that mostly did not happen. Ora's request for the home page got no page back, and a rate limit, server error or timeout is not a block, so the bot test could not run and the door, content, policy, structured-data and metadata rows are unverified rather than failed; the Access layer reads 1 of 40, with no sitemap and no llms.txt. The act layer did answer, with nothing in it: neither a public API nor a developer portal, no OpenAPI specification, and no MCP server or OAuth discovery, so the Usability layer reads 0 of 30, the only zero Usability score in this series. The Discovery layer is the one row in order at 7 of 11, with Wikipedia and Wikidata confirmed and hitachi.com fifth for hitachi. A conglomerate that sells industrial software has a site the scan could not read and no surface it could call; the first fix is a home page that answers.
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 hitachi.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 hitachi.com (ora.ai/score/hitachi.com), read 9 Nov 2026. Vendor claim.
Last reviewed