Your Chicago to Austin itinerary is ready.
Give your AI the right inbox,
not your whole inbox.
Create purpose inboxes. Connect agents to the mail they need. Archive the work when it’s done.
One central inbox, many otter subs
Replace 10+ separate accounts with purpose inboxes. All Mail is a human view that can include every active compartment while Personal stays focused on the main address.
Better email view
Follow the conversation, including who joined. The preview keeps visible headers, recipient changes, and branches legible without inferring hidden context.
Please add the hotel confirmation to this thread.
Create. Connect. Archive.
Create a purpose inbox, connect an agent with fine-grained controls, then retire the whole inbox while retained mail remains available.
One policy layer. REST and MCP are two doors.
Agents bring their own model. OtterMail provides scoped inbox operations and the approval path beneath either interface.
| GET | /api/v1/inboxes |
|---|---|
| GET | /api/v1/search |
| GET | /api/v1/messages/{id} |
| POST | /api/v1/inboxes/{id}/drafts |
| POST | /api/v1/drafts/{id}/send-requests |
| GET | /api/v1/audit |
MCP v2 preview: list scoped inboxes, search, read a message, create a draft, request approval.
Demo data. One authenticated operation counts once across REST and MCP. This landing preview does not connect to a provider.
Capacity for the way you work.
Four paid tiers use the same scope, revocation, audit, and approval vocabulary. Choose room for organized mail and agent operations.
Practical questions, answered plainly.
Scope, sending, archiving, domains, and the product boundary in the language the controls use.
An agent receives the inboxes named in its grant, with the actions you select: read, search, organize, or draft. Send permission is separate, and the demonstrated send path stays behind human approval.
OtterMailGive your agent one inbox to start.
Explore the offline demo: scope access, scan purpose inboxes, follow a conversation, and archive the work.





