Glencore: 41 of 100 on Ora's agent-readiness scan

In short

Glencore scores 41 of 100 on Ora's agent-readiness scan, grade D, read on 12 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. The layers read Discovery 9 of 10, Access 11.67 of 21, Usability 1 of 10. A 733-entry sitemap, no JSON-LD, and Usability at 1 of 10.

The score

Glencore is a mining and commodity trading company based in Baar, Switzerland.

  • 41of 100, grade D
    Ora's agent-readiness scan of glencore.com, read 12 November 2026.
  • 9Discovery, of 10
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 11.67Access, of 21
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 1Usability, of 10
    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: Glencore gives agents little to work with: no WebMCP support, no JSON-LD structured data, and a homepage with no H1 tag.

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.

The door at glencore.com
CheckResultWhat Ora saw
Not blocked by bot detectionPass, 2 of 2Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
Agent crawler reachabilityPass, 1 of 1Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable
robots.txt AI crawler policyPass, 1 of 1AI 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 policyPass, 1 of 1No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://glencore.com/. Declared policy only;
Content without JavaScriptPartial, 1.67 of 5Homepage: 5249 chars of readable text, but no H1 tag. 5 of 5 sampled inner pages have text without JavaScript.
Homepage not hidden from searchPass, 1 of 1No 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.

Reading glencore.com
CheckResultWhat Ora saw
llms.txt existsDid not apply, 0 of 1Can't verify: a bot shield answered our request to glencore.com/.well-known/llms.txt (HTTP 403) instead of the site. That is not counted against the site.
llms.txt formattingFail, 0 of 2No llms.txt found to evaluate quality
Markdown agent docsFail, 0 of 1Missing 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 servingFail, 0 of 1No 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 dataFail, 0 of 2No JSON-LD structured data found on homepage
Organization schema completenessFail, 0 of 1No JSON-LD found - Organization schema missing
Sitemap existsPass, 1 of 1Valid sitemap found at /sitemap.xml with 733 entries
Metadata completenessPass, 1 of 1All metadata signals present: canonical URL, lang="en", og:image, og:type
Page token budgetPass, 1 of 1All 6 measured pages fit an agent context budget (largest ~2K tokens)
Acting through glencore.com
CheckResultWhat Ora saw
MCP server / manifestDid not apply, 0 of 10Can't verify: a bot shield answered our request to glencore.com/.well-known/mcp (HTTP 403); glencore.com/.well-known/mcp.json (HTTP 403) instead of the site. That is not counted against the site.
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsDid not apply, 0 of 8No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
Public API/docs linked from homepageDid not apply, 0 of 4API/docs link found on homepage (/.rest/api/v1/documents/static/c212884a-9152-4454-8556-347644e01349/2025+Modern+Slavery+Statement.pdf) but each page is thin, unreachable, or not HTML/markdown
OpenAPI spec publishedDid not apply, 0 of 8No OpenAPI/Swagger specification found
Developer portalDid not apply, 0 of 5Can't verify: a bot shield answered our request to glencore.com/developer (HTTP 403); glencore.com/console (HTTP 403) instead of the site. That is not counted against the site.
OAuth 2.0 supportDid not apply, 0 of 5Can't verify: a bot shield answered our request to glencore.com/oauth2/authorize (HTTP 403); glencore.com/services/oauth2/authorize (HTTP 403) instead of the site. That is not counted against the site.
Scoped permissionsDid not apply, 0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
CLI tool availableDid not apply, 0 of 3No CLI tool found
WebMCP supportFail, 0 of 8No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations)
Finding Glencore
CheckResultWhat Ora saw
Brand name discoverabilityPass, 3 of 3glencore.com ranks #4 for "Glencore" (searched your brand name alone: no main product term from your homepage qualified)
Developer resource discoverabilityPass, 4 of 4In a search for your API docs, your docs came up at #1 (https://www.glencore.com/.rest/api/v1/documents/static/7a4295e4-3674-45e9-94c4-7d7fb285faff/GLEN-2024-Annual-Report.pdf)

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 17.8 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations).
  2. Content without JavaScript, worth about 5.3 points by Ora's estimate: Homepage: 5249 chars of readable text, but no H1 tag. 5 of 5 sampled inner pages have text without JavaScript.
  3. Product + docs MCP coverage, worth about 4.4 points by Ora's estimate: This bonus needs two MCP servers: one for your product so agents can take actions, and a separate one for your documentation so agents can answer questions from your docs.

Our read

Glencore's site reads well to an agent and gives it nothing to do. The door is open: all four test agents reached the home page and robots.txt allows the AI search crawlers in 3 of 3 checks. The reading is mostly in order: a sitemap of 733 entries, every metadata signal present and text without JavaScript on all 5 sampled inner pages, though the home page carries 5,249 characters and no H1, and without JSON-LD no Organization block says who the company is. Discovery reads 9 of 10. The D comes from the act layer: Usability reads 1 of 10, with neither a public API nor an OpenAPI file, and a bot shield answered the MCP, OAuth and llms.txt probes, so those rows are unverified rather than failed. The API docs link Ora found is a PDF of the 2025 Modern Slavery Statement, which describes the probe more than the company. A D at 41; WebMCP alone is worth about 17.8 points, more than the act layer scores today.

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 glencore.com; a scan of a public site takes a few minutes and needs no account.

Sources

  1. Ora report for glencore.com (ora.ai/score/glencore.com), read 12 Nov 2026. Vendor claim.

Last reviewed