Berkshire Hathaway: 46 of 100 on Ora's agent-readiness scan

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.

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.

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. 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 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.