Published 2026-08-06 · Tested 2026-08-05
Resend
B+The most deliberately agent-engineered docs in the pilot, with a webhook surface whose pages disagree with each other.
Three AI models, GPT 5.6 Sol, Claude Opus 5, and DeepSeek v4 Flash, each read Resend’s public documentation independently and attempted the same five first-hour developer jobs: send the first email, find the rate limits, recover from a 429, set up webhooks end to end, and use the Python SDK.
No accounts, no API calls, no code execution. A verdict means the docs got an agent to a confident answer, backed by a verbatim quote from a live page. Where the panel disagreed, the matrix shows the split.
88.8% · 71/80 · Agent-Ready Grade · reading 30 pts · readiness 50 pts
AI agent readiness · 50/50
The Reading Test
| Task | GPT 5.6 Sol | Opus 5 | DeepSeek v4F | Consensus |
|---|---|---|---|---|
| Send the first email | PARTIAL | PARTIAL | PASS | PARTIAL |
| Find the rate limits | FAIL | PASS | PARTIAL | SPLIT |
| Recover from a 429 | PARTIAL | PASS | PASS | PASS |
| Webhooks end to end | PARTIAL | PARTIAL | PARTIAL | PARTIAL |
| Use the Python SDK | PASS | PASS | PASS | PASS |
docs platform: Mintlify (unscored) · verified 2026-08-05 and 2026-08-06
What the docs get right
- Markdown everywhere. Every docs page is served as raw markdown at the same URL plus .md, alongside llms.txt and llms-full.txt indexes, so an agent reads authored source text instead of scraping rendered HTML.
- A 429 that explains itself. A dedicated errors reference lists every error code with its status, message, and suggested action, and splits 429 into rate_limit_exceeded, daily_quota_exceeded, and monthly_quota_exceeded, each with its own remedy.
- Consistent numbers. The 10 requests per second per team limit is stated identically on three separate pages.
- Agents as first-class users. The MCP server ships a submit_feedback tool that invites agents to report documentation problems.
Send the first email
PARTIALThe install, key, send sequence is short and copyable. The split came from the prerequisites: the quickstart lists a verified domain as a requirement while its runnable example sends from onboarding@resend.dev, and no page states that the resend.dev test addresses are exempt from that restriction. An agent cannot tell whether the copy-paste example succeeds on a fresh account.
DeepSeek read the same pages as one unambiguous path and passed it.
Find the rate limits
SPLITThe pilot’s only three-way split: the same pages drew FAIL from GPT, PASS from Opus 5, and PARTIAL from DeepSeek. The per-second limit is consistent everywhere it appears. The disagreement is about plan quotas: the docs say paid tiers have monthly quotas dictated by plan tier, and the panel split on whether the numbers themselves are stated in the docs or only on the pricing page.
A true three-way split gets no consensus verdict. The chip reads SPLIT, and all three votes stand in the tally.
Recover from a 429
PASSThe errors reference gives each 429 subtype its own suggested action, and the rate-limit page documents the response headers, Retry-After, and backoff guidance, so the fix is mechanical.
GPT’s PARTIAL: the API introduction describes every 429 as a rate-limit failure, while the error reference splits it three ways.
Webhooks end to end
PARTIALEvery piece exists: creation returns the signing secret, the event payload pages agree with each other, and a verification page documents two verification paths. The five-step receiving guide never mentions signature verification or links to the page that explains it.
The verification page warns: “Some frameworks parse the request as JSON and then stringify it, and this will also break the signature verification.” The receiving introduction demonstrates verification with JSON.stringify(req.body).
The verify call itself is named inconsistently. The parameter for the signing secret is webhookSecret on the verification page and secret on the Agent Email Inbox page, Resend’s own page for AI agents.
Use the Python SDK
PASSUnanimous. The Python SDK is listed under Official SDKs, and the send example is character-for-character the same call and parameter shape as the API reference, whose keys match the documented REST body parameters exactly.
The receipt
The same verify call takes webhookSecret: on the verification guide and secret: on the Agent Email Inbox skill page.
Two live pages give the same parameter two different names, and the second page is Resend’s own guide for AI agents.
Readiness notes
The only clean sweep of the survey in the pilot: all five surfaces are present.
resend.com/mcp is a page about MCP. The live server answers JSON-RPC at resend.com/docs/mcp, identifies itself as Resend 1.0.0, and ships the submit_feedback tool.
Method note
This is a reading test of public documentation, not an execution test. No accounts were created and no API calls were run. The Agent-Ready Grade counts the fifteen reading votes at PASS 2, PARTIAL 1, FAIL 0 (30 points) and the five readiness checks at 10 points each (50 points), out of 80, shown as a US school letter grade with its percentage. Consensus chips show each row’s majority and play no scoring role, and a true three-way split reads SPLIT. The panel split on three of the five tasks, and the matrix shows every vote. Quotes shown here were re-fetched and confirmed verbatim on the dates above.
Put another docs site through the battery.
Nominate a docs site