$HEADLESS SYSTEMS
03 / Scorecard / Communications

Resend

B
Headless Index
76/100
JAIRF
69.4/100
AI-Aware
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Resend is solidly built for programmatic consumption. The Headless Index thesis-fit score of 76/100 lands it in the upper-middle of the index, and JAIRF v1.0.0 puts it at 69.4/100 (Level 2, AI-Aware). In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Resend lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Resend is developer-first email API with a clean REST interface and SDKs in Node, Python, Go, Java, Ruby, PHP, .NET, and Rust. Bearer auth, batch sending, templating with React Email, and a streamlined documentation experience. The product is shaped around modern app development workflows.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at resend.com/docs. SDK code generation suggests an internal OpenAPI spec. Schema discoverability is good.[2] An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Emails, contacts, audiences, broadcasts, domains, and API keys are programmable. The resend CLI gives shell access. React Email integration extends template authoring into the developer toolchain.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Resend MCP server has been published. The developer-friendly architecture would make MCP integration straightforward.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Resend webhooks deliver email events (sent, delivered, bounced, complained, opened, clicked) with HMAC signing via Svix. The catalog is appropriate for transactional email. Net assessment: Resend can be operated by agents for the majority of practical workflows. The closest thing to a gap is MCP posture[5], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent18/20
scored

Resend is developer-first email API with a clean REST interface and SDKs in Node, Python, Go, Java, Ruby, PHP, .NET, and Rust. Bearer auth, batch sending, templating with React Email, and a streamlined documentation experience. The product is shaped around modern app development workflows.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 83 operations
  • ·GraphQL endpointDiscovered at https://resend.com/api/graphql, introspection disabled or scoped
  • +SDKs maintained10 (dotnet, go, java, javascript, php, python, ruby, rust, typescript); top by stars: resend/resend-node (908 stars)
  • +SDK recency10 of 10 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
  • +npm weekly downloads5.4M across published packages; top: resend @ 5.4M/week
cite (1)
  • github.sdks@2026-05-19
Headless operation16/20
scored

Emails, contacts, audiences, broadcasts, domains, and API keys are programmable. The resend CLI gives shell access. React Email integration extends template authoring into the developer toolchain.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +API operations exposed83 operations in OpenAPI spec
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • github.sdks@2026-05-19
MCP & agent posture12/20
scored

No first-party Resend MCP server has been published. The developer-friendly architecture would make MCP integration straightforward.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +Official MCP serverhttps://github.com/resend/resend-mcp (512 stars, last commit 1 days ago)
  • Community MCP serversNone found
  • +Agent-friendly SDKs2 TS/JS SDKs available; top: resend (5.4M/week downloads)
cite (1)
  • github.sdks@2026-05-19
Schema observability16/20
scored

REST documented at resend.com/docs. SDK code generation suggests an internal OpenAPI spec. Schema discoverability is good.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://resend.com/openapi.json (OpenAPI 3.0.3, 83 operations)
  • ·GraphQL introspectionGraphQL endpoint at https://resend.com/api/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • github.sdks@2026-05-19
Webhooks & events14/20
scored

Resend webhooks deliver email events (sent, delivered, bounced, complained, opened, clicked) with HMAC signing via Svix. The catalog is appropriate for transactional email.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • github.sdks@2026-05-19
JAIRF · 6 dimensions
FCFoundational Compliance
100/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
61.5/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
46/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
60/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
80/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
70/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:B band: JAIRF=69.4 HeadlessIndex=76

04 / Embed

Show Resend's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Score99 · ADocumentation completeness and SDK shape (~22 checks)April 7, 2026
CLIRank Agent Friendliness90 · ExcellentCLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic ScorecardJAIRF-based scorecard requiring a public OpenAPI specification
THI 76 vs external median 95, delta -19

THI display 76 vs external median 95 (delta -19). Within calibration band.