◎ Discry Score
equinix.com
infrastructure · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
INFRASTRUCTURE · RANK #56 OF 68

Equinix is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Equinix 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 · 50/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.Partial
.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.Fail

Comprehension

55% of score · 62/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.Fail
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Partial
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

  • Equinix's developer.equinix.com returns 403 for all standard discovery URLs (robots.txt, llms.txt, sitemap.xml) — the site redirects to docs.equinix.com which uses Docusaurus
  • OpenAPI specs are downloadable for each API product (Fabric v4, Metal, Network Edge) via Redocly-rendered reference pages — strong for programmatic consumption
  • The Agent Factory repo (equinix/agent-factory) shows investment in agent tooling, and MCP servers exist on Smithery and Glama for Fabric and DCIM Power
  • No error handling documentation exists beyond per-endpoint OpenAPI response codes — an agent would have no recovery guidance when errors occur
  • Comprehensive API catalog organized by product with 20+ API families, but no single overview or llms.txt to help an agent understand the full surface area

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 docs.equinix.com covering the core API families (Fabric, Metal, Network Edge) with structured descriptions and quickstart links
  2. 02Create a dedicated error handling guide documenting common errors across APIs with actionable recovery steps
  3. 03Fix developer.equinix.com to serve robots.txt and sitemap.xml instead of returning 403 — or properly redirect to docs.equinix.com equivalents
  4. 04Add AGENTS.md to equinix/equinix-sdk-python and other SDK repos with context for coding agents integrating Equinix APIs
  5. 05Document rate limits explicitly — currently no rate limit information is publicly accessible for any Equinix API

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.

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

OAuth 2.0 with short-lived access tokens and refresh tokens. OIDC provider support. Pagination via offset/limit parameters. No dedicated error handling or rate limit documentation found. 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