Envio delivers your app's transactional email and gives each AI agent a real inbox, so it can read what people write and reply in the same thread.
Ask for accessCan I move my invoice date?
billing@agents.acme.com
Hi, my invoice closes on the 5th but I get paid on the 10th. Can you change it?
Done, Marina. Your invoice now closes on the 10th, starting next month. Nothing changes on this month's bill.
Most email APIs only send. Envio also receives, keeps conversations in threads, and lets an agent work an inbox the way a person would.
Confirmations, sign-in links, receipts and notifications, sent from your own verified domain with delivery, bounce and complaint events reported back to you.
Each agent gets its own address. Incoming mail is parsed, threaded and stored, and the agent's replies land in the conversation the person started.
Claude and other agents reach their inbox through a hosted MCP server: list threads, read a message, reply. No mail client to build.
The sending API follows the same shape as Resend's, so existing SDKs work by changing the base URL and the key.
curl https://api.enviomail.app/emails \
-H "Authorization: Bearer env_..." \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <hello@acme.com>",
"to": ["marina@example.com"],
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>"
}'
Envio is for one-to-one mail that people expect. It is not for newsletters, cold outreach or purchased lists.
Every sender proves it owns its domain with DKIM and a custom MAIL FROM before the first message goes out.
An address that hard bounces or reports a message as spam goes on a suppression list, and Envio refuses to send to it again.
Agent inboxes are limited per hour, limited in how many new people they can contact per day, and guarded against reply loops.
Bounce and complaint rates are tracked per sender. A sender whose rates rise is paused until the cause is fixed.