--- title: "Samsung Electronics: 62 of 100 on Ora's scan | Am I Ready for Agents?" description: "Samsung Electronics scores 62 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/samsung-electronics-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Samsung Electronics: 62 of 100 on Ora's scan | Am I Ready for Agents? > Samsung Electronics scores 62 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/samsung-electronics-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Samsung Electronics: 62 of 100 on Ora's agent-readiness scan ## In short Samsung Electronics scores 62 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. An API documented 7 of 7, and an /mcp path that redirects to a web page. ## The score Samsung Electronics makes phones, chips, displays and appliances from Suwon, South Korea. - 62of 100, grade C Ora's agent-readiness scan of samsung.com, read 9 November 2026, listed under Identity & Auth. - 14Discovery, of 15 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 37Access, of 58 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 26Usability, of 58 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. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. Ora's one-line summary: Samsung offers strong developer resource discoverability, but lacks an 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 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). | | Agent crawler reachability | Pass, 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable | | robots.txt AI crawler policy | Pass, 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. | | robots.txt agent-user policy | Pass, 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://samsung.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | Homepage: 1915 chars with H1, but 2.2% content ratio is below the 5% target. 1 of 1 sampled inner page has text without JavaScript (4 skipped). | | Homepage not hidden from search | Pass, 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it 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 | Pass, 1 of 1 | Found the llms.txt at https://developer.samsung.com/llms.txt. | | llms.txt formatting | Pass, 2 of 2 | The llms.txt is well-formatted: 41 lines with markdown links, 4,597 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 (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 | Partial, 3 of 4 | JSON-LD Organization found - missing description and url on this entity | | Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: contactPoint, address | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.samsung.com/sitemap.xml with multiple sitemaps entries | | Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type | | Page token budget | Pass, 1 of 1 | All 2 measured pages fit an agent context budget (largest ~2K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Partial, 2 of 6 | /mcp redirects to an HTML page (https://semiconductor.samsung.com/mcp/), not an MCP endpoint | | MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered | | Public API with reachable endpoints | Pass, 7 of 7 | REST API documentation found at https://developer.samsung.com/tizen. Best-of-protocols score: 7/7. | | Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developer.samsung.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://developer.samsung.com | | OAuth 2.0 support | Partial, 2 of 5 | OAuth mentioned on homepage but no standard endpoints found | | Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found | | Multi-language SDK packages | Partial, 1 of 3 | SDK package found only in npm | | CLI tool available | Fail, 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 "Samsung" and Wikidata Q20718 both verified - domain confirmed on both sources | | Brand name discoverability | Pass, 3 of 3 | samsung.com ranks #3 for "Samsung us" | | 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, 3 of 3 | In a search for your API docs, your docs came up at #4 (https://developer.samsung.com/smarttv/develop/api-references/web-api-references.html). | Ora probed the six payment checks and found no x402, MPP, UCP, ACP or AP2 signal, so the pay layer reads 0 of 0. ## 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. OpenAPI spec published, worth about 4 points by Ora's estimate: No OpenAPI/Swagger specification found. 2. Scoped permissions, worth about 3.8 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found. 3. WebMCP support, worth about 3.8 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found. ## Our read Samsung Electronics scores the public API check 7 of 7 and gives an agent a home page of 1,915 characters at a 2.2 percent text ratio. All four agent user agents get in, robots.txt allows the search and training crawlers, the sitemap and metadata are complete, an llms.txt sits at developer.samsung.com and the Organization block lacks its description and URL, so the Access layer reads 37 of 58. On the act layer, developer.samsung.com documents the Tizen REST API in full and an SDK sits on npm, but /mcp redirects to an HTML page on the semiconductor site rather than an MCP endpoint, OAuth is mentioned without standard endpoints, and there is no OpenAPI specification and no declared scopes, so the Usability layer reads 26 of 58. Ora probed the six payment checks and found no x402, MPP, UCP, ACP or AP2 signal, so the pay layer reads 0 of 0. An OpenAPI specification for an API already documented this well is the fix with the most points, about 4. ## 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 samsung.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 samsung.com](https://ora.ai/score/samsung.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/samsung.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.