Resend + MailKite

Resend is a modern email API for developers. MailKite offers the same developer-first experience with inbound email parsing, unlimited free domains, and MCP-native AI agent support.

What you need

• A verified domain with SPF + DKIM published
• Your API key (mk_live_…)
• Resend account (optional — MailKite replaces or complements it)

Send email

MailKite supports both REST API and SMTP — use whichever fits your stack.

# MailKite as a Resend alternative
# Same developer experience, inbound-first

# Resend uses a REST API:
# POST https://api.resend.com/emails
# Authorization: Bearer re_...

# MailKite uses the same pattern:
# POST https://api.mailkite.dev/send
# Authorization: Bearer mk_live_...

# Or use SMTP:
SMTP Host: smtp.mailkite.dev
SMTP Port: 587
SMTP Username: mailkite
SMTP Password: mk_live_...

Receive inbound email (optional)

Resend charges for inbound email parsing. MailKite includes it free.

# Resend inbound email is a paid feature
# MailKite inbound parsing is free

# MailKite inbound webhook
# POST https://your-endpoint.com/webhook
# Payload: { from, to, subject, text, html, attachments }

Test it

Send via MailKite's API or SMTP.

# Test via API
curl -X POST https://api.mailkite.dev/send \
  -H "Authorization: Bearer mk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"from":"hello@yourdomain.com","to":"test@example.com","subject":"Test","text":"Hello from MailKite"}'

Troubleshooting

• Resend is API-first (no SMTP by default). MailKite supports both API and SMTP.
• Resend inbound email is a paid feature. MailKite includes it free on all plans.
• Both use Bearer token auth — swap the base URL and key.

See the SMTP relay docs for the full connection reference, or all integrations for other platforms.