Give every agent an inbox of its own.
Support, sales, ops: one address for each job, on your domain. Mail wakes the agent in its own app.
An agent on your inbox can read all of it.
And nobody can tell who wrote what. Give it its own address: its mail, its key and its limits stay apart from yours.
Mail arrivesIts own inboxIts keyIts agentsupport@acme.devSend and read
Grok BotA routine starts.sales@acme.devDrafts only
PokeDrin texts it.ops@acme.devRead only
ClaudeChecks every hour.Reply, same threadDraft for you to send
sam@example.com
Where's my order?
Grok BotA routine starts.lee@example.com
Can I see a demo?
PokeDrin texts it.ci@acme.dev
Build failed on main
ClaudeChecks every hour.support@acme.dev
Where's my order?
Grok Bot, send and readA routine starts.sales@acme.dev
Can I see a demo?
Poke, drafts onlyDrin texts it.ops@acme.dev
Build failed on main
Claude, read onlyChecks every hour.One address per job
Make support@, sales@ or ops@ on your domain, or start on one of ours with no DNS.One key per agent
Send and read, drafts only or read only, on the inboxes you pick. Any other inbox answers 404.Each agent wakes its own way
A Grok Bot routine, a text to Poke, a signed POST to your URL, or a check on a schedule.
Connect, wake, reply.
The agent asks to connect and you approve one code, and any new wake address. Then mail wakes it and it replies in the thread. Its first mail to a new address waits for a person, unless it's a reply to a verified sender in the same thread on an open desk.
curl -X POST https://api.drin.run/v1/connect \
-H 'content-type: application/json' \
-d '{ "clientName": "Grok Bot", "inboxes": ["support@acme.dev"] }'
# Show the person messageForHuman: a link and a code.
# Once they approve, /v1/connect/token returns the key, once.curl -X POST https://api.drin.run/v1/wake-targets \
-H "Authorization: Bearer $DRIN_KEY" \
-H 'content-type: application/json' \
-d '{ "kind": "generic", "url": "https://agent.acme.dev/drin",
"token": "s3cret", "name": "Support agent" }'
# From an agent's key: 202. Nothing fires until a person approves.curl -X POST https://api.drin.run/v1/emails/$MESSAGE_ID/reply \
-H "Authorization: Bearer $DRIN_KEY" \
-H 'content-type: application/json' \
-d '{ "text": "Sorry about that. A new one ships today." }'
# To a new address: 202 held_for_approval, until a person approves it.
# On an open desk, a reply to a verified sender in this thread goes out.
curl -X POST https://api.drin.run/v1/threads/$THREAD_ID/read \
-H "Authorization: Bearer $DRIN_KEY"Hand this to your agent
Connect Drin to your email: call POST https://api.drin.run/v1/connect, then show me the link.




