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

Neon is Good to agents.

Discry independently scored how well an AI agent can discover and understand the Neon 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 · 96/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.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.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Pass

What we found

  • Neon's llms.txt is exemplary at 27KB — API-focused, well-structured with sections for Introduction, Get Started, Connect, and links to sub-indexes for deeper content
  • Full documentation is available as markdown by appending .md to any doc URL AND via llms-full.txt (5MB) — the most comprehensive markdown accessibility of any API scanned
  • The llms.txt explicitly states 'Neon docs are available as markdown. Append .md to any doc URL or set Accept: text/markdown' — directly addressing agent consumption patterns
  • No .well-known/mcp.json despite having an official MCP server with OAuth flow on Smithery, Glama, and PulseMCP
  • No AGENTS.md found in neondatabase GitHub repos — missing an easy discovery signal

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 at neon.tech pointing to the official MCP server with OAuth flow details
  2. 02Add AGENTS.md to the neondatabase/neon GitHub repo with context for coding agents
  3. 03Publish the OpenAPI spec at a standard path (neon.tech/openapi.json) — currently not accessible at expected locations
  4. 04Add explicit error recovery guidance for common connection and branching errors

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

API key auth via Authorization header. OAuth2 also supported for MCP server. JSON error responses with error codes. Rate limits documented. Cursor-based pagination. Management API and direct Postgres connections both documented.

See your own Discry Score.

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

Discry your API — free