Send, receive and reply
Give every agent a separate inbox. Work with messages, threads and attachments through the API or dashboard.
Explore the email API →
Give your agent an email address. Send a message, receive a reply,
and keep the conversation going — from your code.
Next: connect your agent with an API key or MCP.
Managed in Outflare. Use our email domain or bring your own.
SEE HOW IT WORKS
YOUR AGENT’S EMAIL ADDRESS
A dedicated inbox for your research agent. Messages and attachments stay together.
✓ Ready to connect your agentPOST /v1/workspaces/{workspace}/cloud/agent-mail/brands/{brand}/inboxes
Authorization: Bearer {workspace_token}
{
"username": "research",
"display_name": "Research agent"
}
The API returns your inbox ID and email address.
Your agent can use any model or framework. You control which inboxes it can read and send from.
Using MCP? Start here →EMAIL YOUR AGENT CAN WORK WITH
Sending is only the start. Read the reply, download the attachment, and let your agent take the next step.
Give every agent a separate inbox. Work with messages, threads and attachments through the API or dashboard.
Explore the email API →Get a signed webhook when a message arrives. Fetch its content, run your agent, and reply in the same conversation.
Build a receive workflow →Choose an agentsget.email address or add your own domain. Keep access separate for each brand and each inbox.
Connect a custom domain →API, MCP OR DASHBOARD
Build with HTTP, connect an MCP-compatible agent, or work from the Outflare dashboard. It’s the same brand, the same inbox, the same conversation.
Read the API schemaCreate a key in Outflare and use the brand and inbox identifiers shown there. Examples use placeholder variables.
Read the latest messages
curl --get \
"https://app.outflare.ai/v1/cloud/agent-mail/brands/$BRAND_ID/inboxes/$INBOX_ID/messages" \
--header "Authorization: Bearer $AGENT_MAIL_KEY"
Inbox-scoped key · read permission required
Connect your MCP-compatible client
{
"mcpServers": {
"outflare-agent-mail": {
"type": "http",
"url": "https://app.outflare.ai/v1/cloud/agent-mail/brands/YOUR_BRAND/mcp",
"headers": {
"Authorization": "Bearer ${AGENT_MAIL_KEY}"
}
}
}
}
Client configuration varies. Substitute credentials securely.
BUILD SOMETHING THAT CAN ANSWER BACK
Start with a scoped key, then connect email to the way your agents already work.
Create an inbox in Outflare, scope a key, and read messages with curl.
Read the quickstart → MCPConnect an MCP-compatible client to the inboxes it is allowed to use.
Connect with MCP → EVENTSVerify webhook signatures, handle retries, and fetch the message through the API.
Build the receive flow →COMMON QUESTIONS
No. Agent Mail is a module inside Outflare. AgentsGet.email is the hosted address domain and this marketing site. Signup, login, inbox management and account settings are all in Outflare.
Yes. Custom domains are optional. Add the verification and email records at your current DNS provider, or choose managed DNS. A dedicated mail subdomain helps keep your existing business email separate.
No. These are newly hosted inboxes for your agents. You don’t need to connect an existing personal mailbox.
Create an Outflare account, select a brand, then open Agent Mail. The module shows its availability and setup status in your workspace. This is a paid service; account access, plan availability and usage controls are managed in Outflare.
When service ends, inbox access stops. Retained data can be restored by reactivating within 90 days; after that it is deleted. Deleted email addresses are never reassigned to another customer.
YOUR NEXT STEP
Everything happens in your Outflare workspace.