AgentsReady
Verified deep dive · Comms & data

Resend

Run the agent liveReport a change
3 minTime to key
NoNo-human path
2Human gates
9/10Onboarding score
Domain verificationEmail verification

Fastest path to a key

  1. Sign up at resend.com/signup (email or social login)
  2. Email verification
    Verify email
  3. Fastest agent path: connect remote MCP https://mcp.resend.com/mcp -> browser OAuth consent (no key copy needed); MCP/CLI/API can then create API keys
  4. Alternative: Dashboard > API Keys > Create (Sending access or Full access, optional domain restriction) then `resend login --key re_...`
  5. Domain verification
    Send immediately from onboarding@resend.dev to own address / *@resend.dev test addresses; add + verify a domain (DNS) to send to anyone
  6. Working API key

Biggest gap

No agent-initiated signup or device-flow CLI login; production sending still blocked on domain DNS verification.

Worth copying

Ship the CLI with an explicit agent mode (auto JSON on non-TTY, stable error codes, stdin piping, --idempotency-key) and document it on a dedicated 'CLI for AI agents' page.

Sources (12) · checked 2026-10-11
97Readiness score / 100
L4 Agent-nativeBeats 100% of 1,846 companies
Access20/20
Context20/20
Interfaces32/32
Onboarding19/19
Trust6/9
llms.txt · root
MCP · https://mcp.resend.com/mcp
OpenAPI · https://resend.com/openapi.yaml

Biggest gains

  1. +3 Public status page. Link a status page so agents can tell outages from bugs.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • PASSllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 2 changes, up to +3 points

Each change is ready to paste, filled in for resend.com, with a command to check it worked. Or hand the whole list to your coding agent.

When a call fails, an agent checks status to tell an outage from its own bug.

Where: Footer, docs and llms.txt
Link a public status page (Better Stack, Instatus, Atlassian Statuspage) at https://status.resend.com
from your footer, your docs sidebar and llms.txt.

Add the badge to your README

AgentsReady badge for resend.com
[![AgentsReady](https://agentsready.dev/badge/resend.com)](https://agentsready.dev/c/resend.com)