◎ Discry Score
1password.com
auth · API
B
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 93 (A)
Discry your API →
AUTH · RANK #7 OF 16

1Password is Good to agents.

Discry independently scored how well an AI agent can discover and understand the 1Password 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 · 69/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Pass
llms-full.txtA full-text bundle agents can load in one request.Pass
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.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.Pass

Comprehension

55% of score · 100/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
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.Pass
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.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Pass

What we found

  • 1Password is the top-scoring API in this batch with exceptional agent-readiness — Content-Signal: ai-train=yes in robots.txt, excellent llms.txt, and a 1.9MB llms-full.txt
  • The llms.txt is exemplary: curated index with descriptions, workflow decision guides, and links to .md versions of every page
  • Dedicated AI & Agent Security section in docs covers building with LLMs, agentic autofill, and agent hooks — 1Password is building FOR the agentic era
  • Multiple community MCP servers on all three registries (PulseMCP, Glama, Smithery) for credential management
  • Documentation includes comprehensive quickstarts per audience (developers, administrators) with workflow decision guides

What to change

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

  1. 01Add .well-known/mcp.json pointing to a recommended MCP server implementation
  2. 02Create an official AGENTS.md in the 1Password GitHub org with context for coding agents
  3. 03Consider creating an official 1Password MCP server given the strong community interest
  4. 04Host the Connect API OpenAPI spec at a public URL (currently partial/behind docs)
  5. 05Add the llms.txt link to robots.txt sitemap entries for maximum discovery

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 keyservice accountOAuth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

1Password uses service accounts, API keys, and biometric auth. Connect server REST API documented. Rate limits documented. Structured JSON error responses.

See your own Discry Score.

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

Discry your API — free