Intel: 16 of 100 on Ora's agent-readiness scan
In short
Intel scores 16 of 100 on Ora's agent-readiness scan, grade F, read on 13 November 2026. 2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44. A bot challenge meets every assistant at the home page, before any product does.
The score
Intel is a chipmaker based in Santa Clara, California.
- 16of 100, grade FOra's agent-readiness scan of intel.com, read 13 November 2026, listed under Identity & Auth.
- 5Discovery, of 9Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 1Access, of 40Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 3Usability, of 48Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44.
Ora's one-line summary: Turns agents away at the door: a WAF challenge blocks the homepage, and there is no MCP server, OpenAPI spec or public API.
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 | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass. |
| Agent crawler reachability | Partial, 0 of 1 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged). |
| robots.txt AI crawler policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for search crawlers: WAF/bot challenge (HTTP 403) |
| robots.txt agent-user policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for user-triggered agents: WAF/bot challenge (HTTP 403) |
| Content without JavaScript | Partial, 0 of 5 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage blocked by WAF - cannot read its indexing directives |
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 | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| 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 | Did not apply, 0 of 1 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| JSON-LD structured data | Partial, 0 of 2 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial, 0 of 1 | Homepage blocked by WAF - cannot check Organization schema |
| Sitemap exists | Fail, 0 of 1 | No sitemap found |
| Metadata completeness | Partial, 0 of 1 | Homepage blocked by WAF - cannot check metadata |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 0 of 10 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Fail, 0 of 8 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage | Partial, 0 of 4 | Homepage blocked by WAF - cannot check for docs links |
| OpenAPI spec published | Fail, 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Fail, 0 of 5 | No developer portal found |
| OAuth 2.0 support | Fail, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Brand name discoverability | Partial, 1 of 3 | intel.com ranks #7 for "intel" (searched your brand name alone: we could not read a product term from your site) |
| Developer resource discoverability | Pass, 4 of 4 | In a search for your API docs, your docs came up at #2 (https://www.intel.com/content/www/us/en/developer/tools/oneapi/documentation.html). |
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.
- MCP server / manifest, worth about 9.3 points by Ora's estimate: No MCP server or manifest found.
- Public API with reachable endpoints, worth about 7.4 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
- WebMCP support, worth about 7.4 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
Our read
Intel's read turns on one setting: the bot management in front of intel.com. It challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot at the home page and answered the robots.txt request with a 403, so an assistant sent to look at Intel meets an identity check before it meets a product. Access reads 1 of 40. Because the home page never loaded, the structured data, metadata, indexing directives and documentation links are unverified rather than failed; what Ora could confirm is that there is neither a sitemap nor an llms.txt. Search does better than the site: a query for the API docs put Intel's oneAPI documentation at #2. On the act side, Usability reads 3 of 48, with neither an MCP server nor a public API, and no OpenAPI specification or OAuth support for an agent to work through. The fix worth most is an MCP server, about 9.3 points, though the first decision is about that challenge. An F at 16, earned mostly at the front gate.
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 intel.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.
Sources
- Ora report for intel.com (ora.ai/score/intel.com), read 13 Nov 2026. Vendor claim.
Last reviewed