OUTFLARE AGENT MAIL / DEVELOPERS

Email API for AI agents: send, receive and reply

An email-sending endpoint handles one part of a conversation. Outflare Agent Mail gives your application a persistent inbox, so it can also receive a response, find the thread and reply.

On this page

What the email API gives you

Create hosted inboxes within an Outflare brand. Each inbox has its own address on agentsget.email, or a verified custom domain. Your application can read messages, send new messages, reply, reply-all, forward and work with attachments. The same inbox is visible to your team in the Outflare dashboard.

This is designed for developers building agents that communicate over email: a research agent collecting replies, an operations agent exchanging documents, or an application that needs an address for each workflow. It does not require a connected Gmail or Outlook account.

Choose the right credential

Use an Outflare workspace token for setup and administration. For an agent or application, create an inbox-scoped Agent Mail key. Select the specific inboxes it can access and grant read, send, or both. An inbox key cannot administer brands or create other keys.

Workspace routes start with /v1/workspaces/{workspace}/cloud/agent-mail/brands/{brand}. Inbox-key routes start with /v1/cloud/agent-mail/brands/{brand}. Both use bearer authentication. Put keys in your server-side secret store; never ship them in browser JavaScript.

Read messages with curl

After creating an inbox and scoped key in Outflare, set these variables locally. Use the identifiers shown in the dashboard.

curl --get \
  "https://app.outflare.ai/v1/cloud/agent-mail/brands/$BRAND_ID/inboxes/$INBOX_ID/messages" \
  --header "Authorization: Bearer $AGENT_MAIL_KEY"

Message lists are paginated and return previews; fetch the message endpoint for the full body. Search and thread filters help an agent find the context it needs without loading every message. See the quickstart for the setup and first send.

Build around email events

Register signed webhooks at the brand level and filter by inbox and event. For example, handle message.received by fetching the message and scheduling an agent task. Delivery, bounce and complaint events help your application distinguish provider acceptance from delivery feedback.

Send, reply and forward requests require an Idempotency-Key. Preserve it when retrying the same request. An ambiguous provider outcome is reported as unknown; do not send another message blindly. Sending remains subject to recipient policy, account status and usage controls.

API reference and next steps

The Agent Mail OpenAPI schema describes the customer-facing routes and request fields. Start with one inbox and a key limited to that inbox, then add a webhook when polling is no longer enough.

Agent Mail is a paid Outflare module. Availability and setup status appear in your workspace. Account creation does not itself guarantee that mail transport is enabled.

Build your email workflow in Outflare.

Create your account, select a brand and check Agent Mail availability in your workspace.

Create your Outflare account