
OpenMail – Email API for AI Agents and Inbound Workflows
Dedicated inboxes, threaded email replies, and inbound events for AI agents.

What does OpenMail do, in plain English?
OpenMail gives an AI agent its own working email address. Say your purchasing agent emails a supplier and gets a reply with an invoice. Your app can receive that reply, show the attachment text to the agent, and send a follow-up in the same conversation. OpenMail provides the address and moves the messages. The agent or the workflow you connect decides what to do with each message. The service is operated by UAB All Systems Operational.
Turn a reply into a workflow event
Subscribe to message.received with a signed webhook endpoint if your app can receive public HTTPS requests. Verify the signature, acknowledge the event promptly, and process the message in a background job. Save event_id to avoid a second reply if a delivery is retried. An app that can hold an outbound connection can instead use a WebSocket subscription. Route events by inbox_id when different agents handle different addresses. Reply in the existing thread so the supplier can follow the conversation.
Set up an inbox and test it from both sides
Create a key in the OpenMail console and install clawhub:@openmail/openclaw using openclaw plugins install. Follow the OpenClaw plugin setup to add the channel with a mailbox name and restart the gateway. Use Tool mode for mail on request, Notify for alerts you can review, or Channel if the agent should handle incoming mail autonomously. Send a harmless test message from an address you control, read it through the agent, and verify that your reply arrives in the same thread.
For a script, start with openmail init or create an inbox with POST /v1/inboxes. For a compatible client, use the hosted MCP setup and check its permissions during connection.
Read invoice text and keep the original file available
A successful extraction populates parsedText for supported PDFs, images, Office files, and text formats such as CSV. Extraction skips files over 10 MB and returns up to 50,000 characters per attachment. If text is missing or incomplete, fetch the original with an API key and inspect it before acting on a figure. Supported files and extraction limits
Limit what the agent can access
Give a single-inbox agent a key scoped to that inbox. Use sender rules to allow or block addresses or domains. An MCP client can receive message contents, so review its data terms and optional send permissions. Deleted conversations can spend up to 30 days in Trash and can take up to a further 30 days to be erased after removal. Privacy policy · Service terms
What Free and Pro cover
The published EUR prices checked on November 6, 2026 list three inboxes and 3,000 emails per month on Free, with a cap of 100 outbound emails per day. Pro is €9 per month for 10 inboxes and 10,000 emails, plus metered overage. It supports custom domains. Enterprise is priced separately. Current allowances and overage rates
Frequently asked questions
Does the free plan need a credit card?
No. You can test sending and receiving within the free allowance before selecting a paid plan.
Do I have to share my Gmail or Outlook inbox?
No. Create an address for the agent in OpenMail. Each inbox has its own ID and can have its own API key.
Can incoming mail wake an agent without a public endpoint?
Yes. The OpenClaw plugin uses a WebSocket for inbound delivery, and your own application can also use a subscribed WebSocket connection.
Official resources
- OpenMail on GitHub for the CLI and integration code.
- OpenMail Discord for integration discussions.
- OpenMail service status for incidents affecting delivery, API or MCP.





