Samsung Electronics: 62 of 100 on Ora's agent-readiness scan

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.

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.

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