Email in, structured.
Real inboxes on your domain. Every incoming message is parsed, threaded, and announced to your webhook as signed JSON — ready for your code or your agent.
Free sandbox to integrate · Production from $3/month
Three moves, no MIME parsing.
You never run a mail server or walk a MIME tree. Point the domain, and structured messages start arriving.
One call makes a real address on your domain — support@, agent@, anything. MX setup is guided.
Drin accepts the delivery, runs SPF, DKIM and DMARC checks, and parses headers, body and attachments.
A signed inbound_received event posts the sender, subject and thread to your endpoint — the body is one API call away, and it lands in the dashboard inbox.
The email, and what you get.
— sarah
{ "id": "whd_7c3…", "type": "inbound_received", "createdAt": "2026-06-02T09:14:07.412Z", "occurredAt": "2026-06-02T09:14:07.000Z", "data": { "from": "sarah@gmail.com", "subject": "Re: Your sign-in code", "threadId": "thr_4k2…", "authResults": { "spf": "pass", "dkim": "pass", "dmarc": "pass" }, "testMode": false, "messageId": "msg_9f1…", "senderId": "snd_1b9…" } } // body + attachments: GET /v1/emails/{messageId}/body · /attachments
Whole conversations, not loose mail.
Every exchange is threaded with its full history. Reply from the API, the dashboard, or let your agent answer — the thread keeps the context either way.
How agents use threads →The half of email most APIs skip.
support@ lands in your helpdesk logic as JSON — route by subject, sender, or what the message says.
Give an agent its own address. It reads what arrives over MCP and answers on the same thread.
An inbound reply can start an automation — a winback pause, a handoff, a follow-up sequence.