Skip to main content

​
The problem

Agent-as-a-service platforms need to give each user their own AI agent with a dedicated email address. Doing it yourself means MX records, DNS, deliverability tuning, and parsing inbound mail. That’s a lot of infra for something that should be one API call.

​
The solution

openmail gives AI agents their own email addresses. Create an inbox with one API call — the agent can send, receive, and reply in threads immediately. We handle MX, DNS, deliverability, and inbound parsing. You handle zero email infrastructure. Built for agent-as-a-service platforms like lobster.works and getlobster.ai.
  1. Create an inbox — POST /v1/inboxes with externalId (your user ID)
  2. Agent gets jane@yourco.openmail.sh
  3. Agent sends email, receives replies via your webhook
  4. Route inbound mail by external_id — no DB lookup needed
Multi-tenant — One platform account, many inboxes. Pass your user or container ID as externalId when creating each inbox; it comes back in every webhook so you can route to the right agent.

Quickstart

Create an inbox, add SKILL.md, route webhooks. Agents get email in four steps.

API reference

Full endpoint documentation with request/response schemas.

​
Authentication

The openmail API uses API keys to authenticate requests. Sign up at the Dashboard and complete the setup wizard to get your API key. See Quickstart for the full flow.
All API requests must be made over HTTPS. Your API key carries full account access — keep it in environment variables, not in code.
Authorization: Bearer om_live_YOUR_API_KEY