OpenMail is the email inbox API for Agent-as-a-Service platforms. Provision dedicated inboxes for the agents you ship to customers - send, receive, thread. One API.
# Create an inbox
curl -X POST https://api.openmail.sh/v1/inboxes \
-H "Authorization: Bearer om_live_..." \
-d '{"domain": "openmail.sh"}'
# Response
{
"id": "inb_92ma...",
"email": "agent-x82m@openmail.sh",
"created_at": "2024-03-21T10:00:00Z"
}Traditional email APIs were designed to blast newsletters. OpenMail is designed for two-way communication, real threading, and agents that actually need to act on what they receive.
Replies land in your agent's lap. No polling. The moment an email hits an inbox, your webhook fires - parsed, prioritized, ready for your agent to act on.
Replies stay in thread. Customers hit reply in their email client. Your agent gets it in context. No new UI for them to learn.
Each agent gets its own email. Not shared inboxes, not forwarding. Real identity for the agents you ship.
Attachments, handled. PDFs, CSVs, images - automatically extracted and converted to LLM-ready text. Your agent doesn't need to know what a MIME type is.
Minimal surface area. Maximum leverage. One call to provision. Standard webhooks to receive. That's intentional - your team shouldn't spend a sprint integrating email.
{
"object": "inbox",
"id": "inb_8x92ma29s",
"email": "support-bot@openmail.sh",
"created": 1678901234,
"settings": {
"spam_filtering": true,
"webhook_url": "https://api.myapp.com/hooks",
"allowed_senders": ["*"],
"thread_mode": "conversation"
},
"usage": {
"emails_sent": 142,
"emails_received": 893
}
}Every agent you ship to a customer is a potential inbox. Here's what they can do with one.
Enter your email to continue
Sign in
Browser
One API. Custom domains. Full control over the email layer of your platform.