Opt-in only
Only send to recipients who explicitly opted in. Cold outreach, purchased lists and scraped contacts are prohibited; bulk senders must offer an opt-out and honour it within 7 days. [8]
Guides · email · Everyday developer services
Transactional email API. You verify a sending domain with DNS records (SPF and DKIM), then create an API key.
Researched · not yet run liveLast researched 25 October 2026 · Resend · provider site
One Resend account (team) holds domains and API keys.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Sign in to Resend. If you have no account yet, you create it yourself; verapli does not create accounts.
Where: https://resend.com/login
In Domains, add the domain or subdomain you will send from (for example updates.example.com). Resend then shows the DNS records to add.
Where: https://resend.com/domains
Copy each record from the domain's Records tab into your DNS host exactly as shown. They are TXT and MX or CNAME records for DKIM and SPF; the default Return-Path subdomain is "send".
After the domain verifies, Resend recommends adding a DMARC record (see its DMARC guide for the exact record).
In API Keys, create a key with a name, a permission level and optionally a domain restriction. Copy it straight away; you cannot view the value again after creation.
verapli captures RESEND_API_KEY here by plain code: encrypted in your browser, never shown to AI.
Where: https://resend.com/api-keys
Plain-English summary, not legal advice. Each card links its source.
Only send to recipients who explicitly opted in. Cold outreach, purchased lists and scraped contacts are prohibited; bulk senders must offer an opt-out and honour it within 7 days. [8]
Keep the complaint rate below 0.08% and the bounce rate below 4%; accounts exceeding them may be shut down without warning. [8]
| Env var | Secret | Format | What it is |
|---|---|---|---|
RESEND_API_KEY | secret | re_… | Resend API key used to send email |
Source [7]
The same entry as JSON: /api/v1/entries/resend/email · requirements /api/v1/requirements/resend/email · terms /api/v1/terms/resend/email.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Resend email API, and how long will it take?"
→ tools/call requirements { "provider_id": "resend/email" }Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Resend is not affiliated with verapli.