Nvidia: 77 of 100 on Ora's agent-readiness scan

In short

Nvidia scores 77 of 100 on Ora's agent-readiness scan, grade B, read on 9 November 2026. 93 percent of the 132,085 domains Ora ranks score under 70, and the average score is 44. The highest score in the series, with a JSON-LD block that never says Organization.

The score

Nvidia is a chip designer based in Santa Clara, California, whose accelerators train and run most large AI models.

  • 77of 100, grade B
    Ora's agent-readiness scan of nvidia.com, read 9 November 2026, listed under AI & ML.
  • 14Discovery, of 15
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 38Access, of 50
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
  • 35Usability, of 51
    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.

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

Ora's one-line summary: Nvidia excels at developer resource discoverability and SDK distribution, but lacks WebMCP support for agent integration.

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 nvidia.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, 2 of 2Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable
robots.txt AI crawler policyPass, 2 of 2AI 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, 2 of 2No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://nvidia.com/. Declared policy only;
Content without JavaScriptPass, 3 of 3Homepage: 21731 chars, semantic headings (1 H1 + 8 H2s + 83 H3s), 5.4% content ratio. 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 nvidia.com
CheckResultWhat Ora saw
llms.txt existsPass, 1 of 1Found the llms.txt at https://docs.nvidia.com/llms.txt.
llms.txt formattingPass, 2 of 2The llms.txt is well-formatted: 224 lines with markdown links, 18,321 characters in total.
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 dataPartial, 1 of 4JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is
Organization schema completenessFail, 0 of 2No Organization type found in JSON-LD
Sitemap existsPass, 2 of 2Valid sitemap found at https://www.nvidia.com/sitemap_index.xml with multiple sitemaps entries
Metadata completenessPass, 2 of 2All 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 ~5K tokens)
Acting through nvidia.com
CheckResultWhat Ora saw
MCP server / manifestPartial, 2 of 6MCP mentioned at https://docs.nvidia.com/switch-infrastructure/config-manager/config-manager/overview/mcp but no standard manifest endpoint found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsPass, 7 of 7REST API documentation found at /docs/api. Best-of-protocols score: 7/7.
Public API/docs linked from homepagePass, 3 of 3Documentation site found at https://docs.nvidia.com
OpenAPI spec publishedDid not apply, 0 of 7Can't verify: a bot shield answered our request to nvidia.com/.well-known/openapi.json (HTTP 403) instead of the site. That is not counted against the site.
Developer portalPass, 6 of 6Developer portal found at /developer
OAuth 2.0 supportPass, 5 of 5OpenID Connect discovery endpoint found at https://login.nvidia.com
Scoped permissionsDid not apply, 0 of 5Can't verify: a bot shield answered our request to nvidia.com/.well-known/oauth-protected-resource (HTTP 403) instead of the site. That is not counted against the site.
Multi-language SDK packagesPartial, 1 of 3SDK package found only in npm
CLI tool availablePass, 3 of 3CLI package found on npm: @nvidia/foundations-react-core
WebMCP supportFail, 0 of 5No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 12 of 12 same-origin script bundle(s) for modelContext registrations)
Finding Nvidia
CheckResultWhat Ora saw
Wikipedia / Wikidata entity presencePass, 4 of 4Wikipedia "Nvidia" and Wikidata Q182477 both verified - domain confirmed on both sources
Brand name discoverabilityPass, 3 of 3nvidia.com ranks #1 for "NVIDIA GPU computing"
Category share of voiceDid not apply, 0 of 6Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name).
Developer resource discoverabilityPass, 3 of 3Agent discovered 3 developer-resource types by name (developer portal, MCP server, API docs) across 7 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.

  1. WebMCP support, worth about 4.4 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 12 of 12 same-origin script bundle(s) for modelContext registrations).
  2. JSON error responses, worth about 3.5 points by Ora's estimate: API does not return JSON error responses (or no API detected).
  3. MCP server / manifest, worth about 3.5 points by Ora's estimate: MCP mentioned at https://docs.nvidia.com/switch-infrastructure/config-manager/config-manager/overview/mcp but no standard manifest endpoint found.

Our read

Nvidia's 77 is the highest score in this series, earned on the reading side. All four agent user agents reach nvidia.com, robots.txt allows the search and training crawlers, the home page gives 21,731 characters at a 5.4 percent text ratio under a proper heading tree, five of five sampled pages read, the sitemap and metadata are complete and an llms.txt sits at docs.nvidia.com, so the Access layer reads 38 of 50; the one JSON-LD block carries no identity type. The act layer is real: REST documentation at /docs/api scores 7 of 7 on the public API check, with a developer portal, OpenID Connect discovery at login.nvidia.com, a CLI and an SDK on npm, while the MCP mention resolves to no manifest and a bot shield answered the OpenAPI and scopes probes with 403, not counted against the site, so the Usability layer reads 35 of 51. An Organization type in the JSON-LD would tell an agent what it is reading; WebMCP, at 4.4 points, is the fix Ora values most.

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

Sources

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

Last reviewed