Developer guides for agent email workflows

Start with a working inbox

The quickstart takes you from an Outflare account and brand to a hosted inbox, a scoped key, a message read and a controlled send. Start there if you have not used Agent Mail before.

You do not need to connect Gmail or Outlook, or transfer a domain, to understand the API. Hosted platform addresses use agentsget.email; a verified custom domain can be added later.

Choose how your application connects

Read the email API overview when you want to control HTTP requests from application code or background jobs. Read the email MCP guide when a compatible agent runtime will discover and call tools.

Both interfaces use the same inboxes and enforce credential permissions. The dashboard gives people a way to inspect messages and manage the setup while an application uses the API or MCP.

React to incoming email

The receiving webhook guide covers endpoint setup, raw-body signature verification, duplicate handling, queueing, message retrieval and recovery. Use it when an incoming message should start a workflow instead of relying on repeated polling.

Use your own email identity

The custom domain guide explains manual and managed DNS, ownership proof, DKIM, receiving MX and safe changes alongside existing business email. Choose the DNS approach before changing nameservers or existing mail records.

Run the Python starters

The Python examples include an API client and signed webhook receiver, with local HTTP integration tests. Use them to check a workflow before connecting a real inbox or public endpoint.