# SendGrid — API Agent Score

> Score: 68/100 (Grade: C) | Domain: sendgrid.com | Rubric: 1.0.0 | Checked: July 24, 2026

SendGrid scored 68/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/sendgrid)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 68/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 83/100 (A)
- Developer Experience: 84/100 (A)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 50/100 (D)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 6 of 109 public signatures use loose types (anyTypeRatio=0.055). Investigated: sdk 91%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [warn] Security & governance hygiene — security.txt present but served only at the legacy /security.txt path; missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.twilio.com/en-us/sendgrid; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.twilio.com/en-us/products with a runnable first-call sample. Investigated: docs 100%.
- [warn] Description completeness — 362/391 operations carry a description. Investigated: sdk 93%.
- [pass] Changelog published — Newest official SDK activity 28 day(s) ago. Investigated: sdk 100%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/twilio_sendgrid, 8937 snippets). Investigated: docs 100%, cli 100%, sdk 92%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 60%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 100% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 11 of 50 pages have substantive content differences between markdown and HTML (avg 11% missing). Investigated: docs 60%.
- [pass] Docs structured data — JSON-LD Article markup on 18/20 assessed pages (90%) with dateModified present (1 JS-rendered). Investigated: docs 100%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

SendGrid's API program shows strong fundamentals in design, discovery, and documentation parseability — partners can find and read the surface with confidence. However, the program has two critical gaps that block both human partners and AI agents from integrating reliably: errors are not machine-readable (making automated retry and recovery logic impossible), and there is no runnable, test-backed collection or idempotency guidance for agents to build safe, repeatable workflows. Fixing error semantics and runnable truth should be the immediate priority, followed by agent context and inline code samples to complete the onboarding experience.