◎ Discry Score
cisco.com
devtools · API
C
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 96 (A)
Discry your API →
DEVTOOLS · RANK #26 OF 39

Cisco is Needs Work to agents.

Discry independently scored how well an AI agent can discover and understand the Cisco API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 62/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Pass
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Partial

Comprehension

55% of score · 71/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • Cisco has no llms.txt, llms-full.txt, or .well-known/mcp.json — agents relying on these standard discovery signals will not find Cisco APIs automatically
  • Multiple AGENTS.md files exist across CiscoDevNet repos (Local-RAG-AI-Assistant, cisco-secure-access-python-sdk) showing early adoption of agent-first practices
  • The Meraki API has excellent rate limit documentation with recovery guidance, burst allowances, and best practices — a model for agent-friendly operational docs
  • Strong MCP ecosystem presence with 8+ community servers on Glama and PulseMCP covering Meraki, Webex, ISE, and Catalyst Center
  • OpenAPI spec is publicly maintained at github.com/meraki/openapi with regular releases (v1.70.0 as of May 2026)

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add llms.txt at developer.cisco.com covering the major API families (Meraki, Webex, Catalyst Center) with structured descriptions and links to quickstart guides
  2. 02Add llms-full.txt with comprehensive markdown covering core API operations across Cisco's developer platform
  3. 03Create .well-known/mcp.json referencing the community MCP servers or publish an official Cisco MCP server
  4. 04Move sitemap.xml to the standard /sitemap.xml path — currently only referenced via robots.txt at non-standard /data/sitemaps/ paths
  5. 05Add error recovery guidance beyond HTTP status codes — the Meraki error page lacks actionable fix steps for most error scenarios

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

api_keyoauth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Meraki API documents API key and OAuth 2.0 auth with clear comparison table. Error responses are JSON with errors array. Rate limits well-documented at 10 req/s per org with burst allowance. RFC5988 Link header pagination with startingAfter/endingBefore tokens. No idempotency key support documented.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free