Cisco: 32 of 100 on Ora's agent-readiness scan
In short
Cisco scores 32 of 100 on Ora's agent-readiness scan, grade D, read on 14 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. The developer docs rank first in search, but the firewall stops agents before they find them.
The score
Cisco is a networking equipment and software company based in San Jose.
- 32of 100, grade DOra's agent-readiness scan of cisco.com, read 14 November 2026, listed under Infrastructure.
- 6Discovery, of 9Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 12Access, of 38Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 9Usability, of 56Whether 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.
25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.
Ora's one-line summary: Bot detection challenges agents at the door, and the homepage shows no content without JavaScript.
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 | Fail, 0 of 2 | No JSON-LD structured data found on homepage |
| Organization schema completeness | Fail, 0 of 1 | No JSON-LD found - Organization schema missing |
| Sitemap exists | Fail, 0 of 1 | No sitemap found |
| Metadata completeness | Pass, 1 of 1 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Page token budget | Pass, 1 of 1 | All 4 measured pages fit an agent context budget (largest ~3K tokens) |
| 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 | Pass, 8 of 8 | API described in documentation at https://developer.cisco.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://cisco.com/graphql is reachable; |
| Public API/docs linked from homepage | Pass, 4 of 4 | Documentation site found at https://developer.cisco.com |
| OpenAPI spec published | Fail, 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 5 of 5 | Developer documentation portal found at https://developer.cisco.com |
| OAuth 2.0 support | Did not apply, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Did not apply, 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 | cisco.com ranks #7 for "cisco" (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 #1 (https://developer.cisco.com/docs). In a search for your MCP server, SDK or CLI. |
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 7.9 points by Ora's estimate: No MCP server or manifest found.
- OpenAPI spec published, worth about 7 points by Ora's estimate: No OpenAPI/Swagger specification found.
- WebMCP support, worth about 6.3 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
Our read
Cisco's read turns on its own firewall. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot at the home page, and robots.txt answered with a 403 challenge, so Ora could not even read the policy; the rows for content, indexing and markdown behind that wall are unverified rather than failed. A challenge is an identity check that verified crawlers can pass, which makes this a setting to tune more than a wall to tear down. Past the door, the developer story is better than the score suggests: a search for Cisco's API docs put developer.cisco.com first, and an NLWeb /ask endpoint exists, though it answers 403 without authentication. What agents cannot find is anything machine-readable to act on. Ora saw neither an OpenAPI specification nor an MCP server, and the site shows no sitemap, llms.txt or JSON-LD. The fix worth most is an MCP server, about 7.9 points. A D at 32: the networking company's own network is what keeps the agents out.
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 cisco.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 cisco.com (ora.ai/score/cisco.com), read 14 Nov 2026. Vendor claim.
Last reviewed