Agent Mail for AI Agents and Digital Employees

What is agent mail?

Agent mail is email that an AI agent can use through software tools. A dedicated agent address gives customers and teammates a familiar way to contact it, while an API or MCP connection lets your application send messages and read available replies.

Mailrun provides the email channel and its communication records. Your agent decides how to respond using the instructions, business information, and tools you connect. You choose which actions it may take and when a person needs to approve a response.

Digital employee mail in a real workflow

Suppose Sara is your customer-support agent. A customer emails her dedicated address with a setup question. Your application retrieves the message, gives the agent the relevant product information, and sends its approved response through the same Mailrun identity.

If the request needs a person, your application can pass the conversation to your support team. Mailrun carries the email; your support tools and escalation rules determine who handles it next. The example illustrates an integration you build, not an employee supplied by Mailrun.

See the customer-support agent workflow

Send email and read replies through API or MCP

Connect a compatible MCP client or call the HTTP API from your application. Give the integration only the scopes it needs. After domain and mailbox setup are complete, it can submit a message, inspect message records, and retrieve available email content.

An accepted send is still being processed; it is not proof that the recipient received it. Check the message status and use a test inbox you control to verify delivery and replies. Message history is communication data, not automatic memory for your model.

Follow the send-and-reply API quickstart

Keep the address when you change agents

Changing a model or replacing your agent application does not require a new Mailrun email identity. Keep the same contact address while you reconnect the integration, move the context it needs, and test its responses.

That continuity applies to the identity you keep in Mailrun. Your application is responsible for migrating its own memory, tools, and business records. Deleting the identity is a different action from changing the agent connected to it.

Understand agent identities and digital employee IDs

Start with a small, controlled conversation

Set a daily sending cap for the identity, keep its key private, and test with a recipient you control. Review the first replies before connecting a wider workflow. The account allowance and identity cap bound sending; your application still controls the content and recipients.

Agent Identities access is coming soon. Request Access to tell us about your workflow. These guides explain the integration so you can plan ahead; requesting access does not create an account or start a subscription.

See the MCP setup guide