Trafigura: 56 of 100 on Ora's agent-readiness scan

In short

Trafigura scores 56 of 100 on Ora's agent-readiness scan, grade C, read on 11 November 2026. 60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44. Open to every agent, well labelled, and nothing yet for an agent to do.

The score

Trafigura is a commodity trading house based in Singapore and Geneva.

  • 56of 100, grade C
    Ora's agent-readiness scan of trafigura.com, read 11 November 2026.
  • 5Discovery, of 6
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 16.33Access, of 23
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 6Usability, of 15
    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.

60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44.

Ora's one-line summary: Trafigura has solid crawler access, sitemap, and structured data, but lacks WebMCP support for agents to interact with its site.

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 trafigura.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://trafigura.com/. Declared policy only;
Content without JavaScriptPartial, 3.33 of 5Homepage: 3621 chars with H1, but heading hierarchy skips H2 to H6. 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 trafigura.com
CheckResultWhat Ora saw
llms.txt existsFail, 0 of 1No llms.txt found at https://trafigura.com/llms.txt. Publish it at the site root, where agents that follow the llms.txt spec look for it.
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 dataPass, 2 of 2Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s))
Organization schema completenessPartial, 0.5 of 1Organization schema found but missing: contactPoint, address
Sitemap existsPass, 1 of 1Valid sitemap found at https://www.trafigura.com/sitemap.xml with 1289 entries
Metadata completenessPass, 1 of 1All metadata signals present: canonical URL, lang="en-US", og:image, og:type
Page token budgetPass, 1 of 1All 6 measured pages fit an agent context budget (largest ~2K tokens)
Acting through trafigura.com
CheckResultWhat Ora saw
MCP server / manifestDid not apply, 0 of 10No MCP server or manifest found
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 4No public API or documentation page linked from homepage
OpenAPI spec publishedDid not apply, 0 of 8No OpenAPI/Swagger specification found
Developer portalDid not apply, 0 of 5No developer portal found
OAuth 2.0 supportPass, 5 of 5OpenID Connect discovery endpoint found at https://trafigura.com
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 1 of 1 same-origin script bundle(s) for modelContext registrations)
Finding Trafigura
CheckResultWhat Ora saw
Brand name discoverabilityPass, 3 of 3trafigura.com ranks #4 for "Trafigura Commodities"
Developer resource discoverabilityDid not apply, 0 of 4In a search for your API docs, none of the 10 results is your official docs

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 1 of 1 same-origin script bundle(s) for modelContext registrations).
  2. 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.
  3. ARD discovery, worth about 3.7 points by Ora's estimate: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json.

Our read

Trafigura's site is easy for an agent to find and read, and gives it nothing to do. The door is open: all four test agents reached the home page, robots.txt allowed the AI search crawlers in 3 of 3 checks, and nothing restricts the agents a user sends. What they can read is in good order: a sitemap of 1,289 entries, complete metadata, an Organization block with name, description, url and sameAs, and text without JavaScript on all 5 sampled inner pages, though the home page headings jump from H2 to H6. There is no llms.txt. Discovery reads 5 of 6. The act layer is where the score stops: an OpenID Connect endpoint answers, but there is neither a public API nor a developer portal, and no MCP server; Usability reads 6 of 15. For a trading house the agents that matter most are the ones reading about it, and those are well served. A C at 56, with WebMCP alone worth about 18 points.

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

Sources

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

Last reviewed