Sony: 24 of 100 on Ora's agent-readiness scan
In short
Sony scores 24 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. Six agents blocked, a portal behind them, and a brand search that lost the brand.
The score
Sony is an electronics, games, music and film group based in Tokyo.
- 24of 100, grade FOra's agent-readiness scan of sony.com, read 9 November 2026, listed under Identity & Auth.
- 9Discovery, of 17Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 10Access, of 55Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 7Usability, of 55Whether 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.
9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.
Ora's one-line summary: Sony provides a developer portal with public API endpoints, but lacks OpenAPI specifications and OAuth 2.0 support.
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 | Fail, 0 of 2 | Agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended |
| Agent crawler reachability | Fail, 0 of 2 | No major AI crawler can reach the homepage - ChatGPT-User: blocked, ClaudeBot: blocked, Google-Extended: blocked, ora-agent: blocked, DeepSeekBot: blocked |
| robots.txt AI crawler policy | Partial, 0 of 2 | robots.txt blocked by WAF/bot protection - cannot verify AI crawler policy |
| robots.txt agent-user policy | Partial, 0 of 2 | robots.txt blocked by WAF/bot protection - cannot verify agent-user policy |
| Content without JavaScript | Partial, 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
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 | Partial, 0 of 1 | A file is present at https://docs.sony.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text 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 | Did not apply, 0 of 1 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| 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 | Partial, 1 of 2 | Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type |
| 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 | Pass, 7 of 7 | API described in documentation at https://docs.sony.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://sony.com/graphql is reachable; |
| Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://docs.sony.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://docs.sony.com |
| OAuth 2.0 support | Fail, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Fail, 0 of 5 | No scoped permissions or security schemes found |
| Multi-language SDK packages | Fail, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Fail, 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 | error, 0 of 4 | Wikipedia and Wikidata presence could not be verified - try rescanning |
| Brand name discoverability | Pass, 3 of 3 | sony.com appears at position #1 in a clean brand-name search for "sony identity auth" (2 total matches) |
| 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 | Pass, 6 of 6 | Agent discovered 2 developer-resource types by name (API docs, developer portal) across 2 pages |
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.
- MCP server / manifest, worth about 4.8 points by Ora's estimate: No MCP server or manifest found.
- OpenAPI spec published, worth about 4.2 points by Ora's estimate: No OpenAPI/Swagger specification found.
- OAuth 2.0 support, worth about 4 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.
Our read
Sony blocks every agent and keeps its developer portal behind the same wall. GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended and Applebot-Extended were blocked at the door, robots.txt was blocked by the same protection and the home page came back as a security page, so the door, content and policy rows are unverified rather than failed; there is no JSON-LD and no sitemap, the metadata carries one of four signals and the llms.txt at docs.sony.com returns an HTML page, so the Access layer reads 10 of 55. The act layer is docs.sony.com, a real documentation site and portal whose API has no machine-verifiable surface, with no OpenAPI specification, no OAuth discovery and no MCP server, so the Usability layer reads 7 of 55. The brand search ran on sony identity auth, a term that describes the probe rather than the company. An electronics group whose products ship with assistants built in has a site those assistants cannot enter; the block is the row to change.
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 sony.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 sony.com (ora.ai/score/sony.com), read 9 Nov 2026. Vendor claim.
Last reviewed