The Resend alternative that also receives and forwards
Resend is a great sending API. ThreadCamp speaks the same send payload - so migration is a base-URL change - and adds real inbound inboxes, threads and forwarding Routes so your agents can receive and reply, not just send.
Resend vs ThreadCamp
| Point | Resend | ThreadCamp |
|---|---|---|
| Sending | Excellent transactional sending | Resend-compatible send endpoint + scheduled_at |
| Inbound | Inbound webhook, but no inbox primitive or threads | Real inboxes with threads, reply/forward, labels |
| Forwarding | No forwarding-to-external-address | Catch-all + alias Routes with SRS |
| Agent tooling | No MCP server | Hosted + stdio MCP, sandbox keys |
ThreadCamp is the email API for AI agents: inboxes, sending and forwarding with SRS behind one key.
Other alternatives
Questions
Can I migrate from Resend without rewriting?
Mostly yes - POST /v1/emails accepts the Resend payload shape, so you change the base URL and key. You then gain inbound inboxes and forwarding on top.
Switch in an afternoon.
No credit card. Full API, MCP and webhooks on the free tier.