◎ Discry Score
sendgrid.com
communication · API
C
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
COMMUNICATION · RANK #15 OF 24

SendGrid is Needs Work to agents.

Discry independently scored how well an AI agent can discover and understand the SendGrid 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 · 60/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.Partial
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Partial
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.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.Partial

Comprehension

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

What we found

  • An agent can find SendGrid's complete OpenAPI spec via the twilio/sendgrid-oai GitHub repo, enabling full programmatic API discovery.
  • SendGrid docs offer a 'View as Markdown' feature on every page, making content directly consumable by LLMs without scraping overhead.
  • The llms.txt exists only at the Twilio parent level (292KB covering all products), making it impractical for an agent specifically looking for SendGrid email API guidance.
  • No AGENTS.md or .well-known/mcp.json exists, despite multiple third-party MCP servers being available in registries.
  • Rate limit documentation includes actionable recovery guidance with specific headers to check, which helps agents self-correct on 429 errors.

What to change

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

  1. 01Create a SendGrid-specific llms.txt at docs.sendgrid.com covering core email sending workflows, authentication, and key endpoints in under 50KB.
  2. 02Add an AGENTS.md to the sendgrid-nodejs or sendgrid-python repos with SDK usage patterns, common pitfalls, and workflow examples.
  3. 03Publish a .well-known/mcp.json pointing to the official SendGrid MCP server or tool declarations for core operations.
  4. 04Enhance error documentation with specific recovery steps for each error code (currently only lists codes without actionable fix guidance for most errors).
  5. 05Add llms-full.txt with comprehensive API documentation in a single markdown file optimized for agent consumption.

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 key (Bearer token)Basic authentication (with API key as password)✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Well-documented execution characteristics including structured JSON error responses with field-level detail, rate limit headers (X-RateLimit-Limit/Remaining/Reset), and clear auth documentation. 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