Answers in context, not in a queue
Reply drafts land in the reply box; campaign copy lands in the composer; a rewrite keeps your own subject. It is ordinary editable text, and the send button is still yours.
AI & developer API
AI that answers where you're working
Ask for a reply and the draft lands in the reply box. Ask for campaign copy and it lands in the composer. Nothing sends until you press send.
Mailbase's agent runs inside the product, on the model you choose. Requests with somewhere to put an answer are answered in place; open questions open the assistant, which can search your mail, read a thread, look up a contact and propose actions. Inbound mail is classified as it arrives, with tags proposed rather than applied. Everything the app does is also reachable over a REST API with a published OpenAPI contract.
It proposes, you decide
Suggested tags appear as dashed chips beside the real ones, stored apart from applied tags so a guess is never mistakable for a decision. Rejecting one stops it being proposed again. No path in the product sends mail unattended.
Your model, your cost
Run on the included credits or connect your own key or ChatGPT subscription, unmetered. Every AI surface resolves the same model, so drafting, triage and the assistant all speak with one voice.
What it ships with
- In-place drafting for replies, campaigns and the composer
- An assistant that searches mail, reads threads and proposes actions
- Inbound classification with tags proposed, never applied
- Bring your own model — OpenAI-compatible, ChatGPT or the platform default
- REST API with an OpenAPI contract, scoped tokens and signed webhooks
Try it in your workspace.
Free to start. No credit card. Self-hosted or managed sending.
Start free