Issue a real inbox.
Create an address for one agent, one workflow, or an entire fleet. Each mailbox is isolated inside your tenant.
POST /v1/inboxesEmail infrastructure for AI
Give agents a real email address, threaded conversations, and an API to reply—while your team keeps policies, delivery history, and audit visibility.
signature verified · thread_7k2 · delivery attempt 1
From address to action
A clean interface for the outside world. Structured events and durable context on the inside.
Create an address for one agent, one workflow, or an entire fleet. Each mailbox is isolated inside your tenant.
POST /v1/inboxesMessages arrive as signed webhook events with the sender, subject, body, attachments, and conversation context your runtime needs.
email.received · HMAC signedLet the agent reply through the API. Reverbin preserves the thread, applies policy, and leaves a delivery record a human can inspect.
POST /v1/threads/:id/replyOne system, two points of view
Agents get a simple interface to the world. Humans keep the context and controls that make automation trustworthy.
Receive mail, understand the full thread, and reply through a predictable API—without borrowing a person's mailbox or credentials.
See what arrived, what the agent sent, and where delivery failed. Add policies and approval steps around sensitive actions.
Built for real workflows
Use Reverbin anywhere an automated system needs to communicate with people and businesses on their own terms.
Give a service agent durable threads for customer questions, follow-ups, and escalation to a human operator.
Route onboarding and account mail to a purpose-built address instead of sharing access to a personal or team mailbox.
Keep receipts, invoices, questions, and follow-ups in an inspectable record tied to the agent doing the work.
Automate the predictable path, hold risky sends for approval, and hand the complete conversation to a person when needed.
Security & operations
Email can trigger consequential actions. Reverbin gives teams the primitives to verify, constrain, and review agent communication.
HMAC signatures let your runtime authenticate Reverbin events before processing message content.
Tenant-specific API keys maintain clear boundaries between teams, environments, and agent fleets.
Apply recipient and sending rules, or route sensitive messages into a human approval workflow.
Inspect webhook attempts and outbound activity so failures are visible and recoverable.
Preserve the relationship between inboxes, threads, messages, agent actions, and operator decisions.
Straightforward pricing
Every plan includes real inboxes, the API, threaded conversations, and signed webhook events.
Test a real agent workflow before committing to paid volume.
For solo builders shipping production agent email flows.
For teams running multiple agents and higher-volume workflows.
Custom domains, volume, deployment needs, and support.
Paid plans are managed securely through hosted billing. Limits are monthly and subject to the Terms of Service.
Reverbin is email infrastructure built for AI agents, with an operator interface for the humans responsible for them. Agents use the API and webhooks; humans can inspect inboxes, threads, delivery activity, and settings.
Yes. You can create dedicated mailboxes for individual agents or workflows. The free plan currently includes two mailboxes, with larger limits on paid plans.
Reverbin stores the message in its thread and sends a signed webhook event to your endpoint. Your runtime can verify the signature, process the content, and reply through the API.
Yes. The operator-facing mail console keeps inbox, sent, thread, and delivery context visible. Policy and approval mechanisms can also place a human in the loop before a sensitive send.
Webhook delivery attempts are recorded so operators can inspect status, attempts, and errors. Agent runtimes should also use idempotency and safe retry behavior.
Yes. The Free plan includes two mailboxes, 2,000 emails per month, and one webhook endpoint. You can upgrade later from Billing.
Open the channel
Start free, connect one webhook, and put your first agent into a conversation.