FAQ
Everything developers and agents ask about Bavimail
Ten quick answers covering pricing, SDKs, inbound email, webhooks, domain verification, and how AI agents get their own email identity. Deeper detail lives in the docs.
Typical path
01Verify a domain
02Send your first event-driven email
03Subscribe to delivery and engagement webhooks
04Monitor reputation, suppressions, and analytics
Questions
Frequently asked
Short, direct answers. If you are stuck on something that should be here, let us know.
- What is Bavimail?
- Bavimail is an email API built for AI agents and developer workflows. It supports outbound transactional email, inbound email parsing via webhooks, programmatic domain verification (SPF, DKIM, DMARC), and per-agent inbox identities — all through a REST API and typed SDKs.
- How is Bavimail different from Resend, SendGrid, or Postmark?
- Those services are optimized for human senders triggering email from a dashboard or a single transactional flow. Bavimail is API-first and agent-first: two-way inbox support, webhook-driven inbound parsing, programmatic domain verification without manual DNS pasting, and agent-specific identities are first-class, not add-ons.
- Do I need a credit card to start?
- No. You can start on the free plan without a credit card, send and receive email, verify a domain, and wire up webhooks. Upgrade when you need more included capacity or higher rate limits.
- Which languages and SDKs are supported?
- Official TypeScript and Python SDKs are published and documented at /docs/sdks. The REST API is language-agnostic, so any HTTP client works — and the OpenAPI specification at /docs/api is designed to be consumed by agents as tool definitions.
- How does inbound email work?
- Point an MX record at a Bavimail-verified domain or alias. When email lands, Bavimail parses headers, body (plain and HTML), and attachments, then delivers a signed webhook payload. Attachments come back as pre-signed URLs the agent can fetch directly — no giant inline blobs.
- How does Bavimail handle webhook signatures and retries?
- Every webhook is signed with an HMAC header (x-webhook-signature) and timestamped (x-webhook-timestamp). Your handler verifies both and returns 2xx to acknowledge. On non-2xx or timeout, Bavimail retries with exponential backoff. The 13 supported event types are documented at /docs/webhooks.
- Can an AI agent own its own email identity?
- Yes — that is a first-class workflow. Each agent can get its own inbox alias on a verified domain, send under that alias, and receive parsed inbound mail scoped to that alias. See /docs/agent-onboarding for the full setup.
- Is domain verification automated?
- Verification itself is DNS-dependent, but the record generation and polling are both programmatic. You hand Bavimail a domain via the API, Bavimail returns the exact SPF, DKIM, and DMARC records to publish, and the verification endpoint returns a status you can poll from your agent until it flips to verified. No human-in-the-loop required.
- How are API keys managed?
- Create API keys per environment and per agent via the dashboard or the API itself. Keys are bearer tokens — authenticate every request with Authorization: Bearer sk_... headers. See /docs/authentication for creation, rotation, and revocation.
- Where do I see live pricing?
- The pricing page at /pricing shows the current commercial catalog, pulled from our billing provider so the numbers always match checkout. If you need custom pricing for dedicated infrastructure or a larger commercial arrangement, reach out from that page.
Need pricing context?
See the plan structure, retention windows, and overage model before you ship.
View pricingNeed implementation help?
Use the docs hub for quickstarts, API concepts, SDKs, and webhook guides.
Read docsNeed migration proof?
Compare Bavimail against incumbent options before you change providers.
Compare providers