--- title: "Berkshire Hathaway: 46 of 100 on Ora's scan | Am I Ready for Agents?" description: "Berkshire Hathaway scores 46 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/berkshire-hathaway-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Berkshire Hathaway: 46 of 100 on Ora's scan | Am I Ready for Agents? > Berkshire Hathaway scores 46 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/berkshire-hathaway-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Berkshire Hathaway: 46 of 100 on Ora's agent-readiness scan ## In short Berkshire Hathaway scores 46 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. A list of links with no robots.txt, scored as permission by default. ## The score Berkshire Hathaway is a holding company based in Omaha whose site is famously plain: a list of links to its subsidiaries and filings. - 46of 100, grade D Ora's agent-readiness scan of berkshirehathaway.com, read 9 November 2026. - 5Discovery, of 8 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 7Access, of 37 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 7Usability, of 12 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: Robots.txt AI crawler policy is in place, but WebMCP support is missing. ## 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 | Partial, 0 of 2 | Bot management challenged GPTBot, ClaudeBot, ChatGPT-User. A challenge is an identity check that verified crawlers pass, so this is not proof agents are blocked - but unverified agents will not get through. | | Agent crawler reachability | Partial, 0 of 2 | Bot management challenged ChatGPT-User, ClaudeBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, ClaudeBot: challenged). | | robots.txt AI crawler policy | Pass, 2 of 2 | Training: 12/12. Search: 18/18 page/crawler pairs permitted. No robots.txt (HTTP 404); crawl permission defaults to allowed. | | robots.txt agent-user policy | Pass, 2 of 2 | No robots.txt (HTTP 404); crawl permission defaults to allowed. No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user). | | Content without JavaScript | Partial, 1 of 3 | 1248 chars of readable text, but no H1 tag | ## 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 | 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 | Fail, 0 of 2 | No sitemap found | | Metadata completeness | Fail, 0 of 2 | No metadata signals found - missing: canonical URL, HTML lang attribute, og:image, og:type | | Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Did not apply, 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 | Did not apply, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) | | Public API/docs linked from homepage | Did not apply, 0 of 3 | No public API or documentation page linked from homepage | | OpenAPI spec published | Did not apply, 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 tool-attribute forms and no document.modelContext / navigator.modelContext usage found | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q217583 (Berkshire Hathaway) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage | | Brand name discoverability | Partial, 1 of 3 | berkshirehathaway.com appears once in brand-name search results for "BERKSHIRE HATHAWAY INC." (position #4 out of 9) | | 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 | Did not apply, 0 of 3 | Agent struggled to find developer resources by name - only 1 result(s) out of 10. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation | 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 18.5 points by Ora's estimate: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found. 2. Brand name discoverability, worth about 5.6 points by Ora's estimate: berkshirehathaway.com appears once in brand-name search results for "BERKSHIRE HATHAWAY INC." (position #4 out of 9). 3. Agent auth discovery metadata, worth about 3.7 points by Ora's estimate: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: berkshirehathaway.com, api.berkshirehathaway.com. ## Our read Berkshire Hathaway's site is a list of links, and the scan reads it as exactly that. There is no robots.txt at all, which Ora scores as permission by default, 12 of 12 and 18 of 18; the bot test was challenged for GPTBot, ClaudeBot and ChatGPT-User, so the door row is unverified rather than failed. The page gives 1,248 characters without an H1 and carries none of the four metadata signals, neither JSON-LD nor a sitemap, and no llms.txt, so the Access layer reads 7 of 37. The act layer does not exist, and the Usability layer has a maximum of 12; the WebMCP estimate of 18.5 points is large only because so few checks apply. The domain appears once, in fourth place, in a search for the company's own name, with the Wikidata item confirmed and no Wikipedia article matched. A page an agent can read is not yet a page that tells it what it is reading; an H1 and an Organization block would. ## 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 berkshirehathaway.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 berkshirehathaway.com](https://ora.ai/score/berkshirehathaway.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/berkshirehathaway.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.