Give your AI agent its own email identity
Two-way email infrastructure for AI agents. Create aliases, send and receive email.
Why Agents Need Email Identity
Most email APIs assume a human is composing messages. AI agents need:
- A persistent address: An alias the agent owns, so replies come back to it.
- Two-way capability: Send outbound and receive inbound on the same address.
- Programmatic access: No UI required -- everything via API.
- Conversation threading: Automatic thread tracking via
In-Reply-ToandReferencesheaders.
5-Line Setup
Create an alias and send your first agent email:
import { BaviMail } from 'bavimail'
const client = new BaviMail()
const alias = await client.aliases.create({ domainId: 'dom_abc123', localPart: 'agent' })
const email = await client.emails.send({
aliasId: alias.id,
toEmail: 'customer@example.com',
subject: 'Your request has been processed',
body: '<p>Hi, your support ticket #1234 has been resolved.</p>',
})Your agent now has the address agent@mail.yourcompany.com and can both send and receive email.
Use Cases
Support Agent
An AI agent that monitors inbound email, understands the request, and replies with a resolution or escalates to a human.
Notification Agent
An agent that sends transactional emails (order confirmations, password resets, status updates) triggered by events in your system.
Outreach Agent
An agent that sends personalized outreach email on a schedule, tracks opens and clicks, and adjusts messaging based on engagement.
Workflow Agent
An agent that receives structured data via email (approvals, form submissions, reports) and triggers downstream actions in your pipeline.
AI-Consumable Docs
BaviMail publishes machine-readable documentation for AI agents:
/llms.txt: Structured index of all documentation sections./llms-full.txt: Full documentation content, concatenated for context windows.
Point your agent's retrieval system at these endpoints for up-to-date API reference without scraping HTML.