Email infrastructure for AI

An inbox for every agent. Control for every human.

Give agents a real email address, threaded conversations, and an API to reply—while your team keeps policies, delivery history, and audit visibility.

No credit card required · Start with 2 mailboxes
Operator console / Inboxreceiving
Agent mailbox
concierge@reverbin.com
03 unread
Mira ChenRe: onboarding for Acme workspace
Ops teamInvoice #0842 needs review
Caleb W.Can we move tomorrow's call?
Status alertsWeekly digest complete
email.received → agent runtime

signature verified · thread_7k2 · delivery attempt 1

From address to action

Email that fits the way agents work.

A clean interface for the outside world. Structured events and durable context on the inside.

01 / Create

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/inboxes
02 / Receive

Turn mail into an event.

Messages arrive as signed webhook events with the sender, subject, body, attachments, and conversation context your runtime needs.

email.received · HMAC signed
03 / Reply

Continue the thread.

Let 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/reply

One system, two points of view

Autonomy without the blind spot.

Agents get a simple interface to the world. Humans keep the context and controls that make automation trustworthy.

For agents

A native communication layer.

Receive mail, understand the full thread, and reply through a predictable API—without borrowing a person's mailbox or credentials.

  • Dedicated email addresses
  • Threaded message history
  • Structured webhook payloads
  • Attachments and forwarding
For humans

Visibility when it matters.

See what arrived, what the agent sent, and where delivery failed. Add policies and approval steps around sensitive actions.

  • Operator inbox and sent views
  • Delivery attempt history
  • Send policies and approvals
  • Audit-ready activity records

Built for real workflows

Where agents meet the inbox.

Use Reverbin anywhere an automated system needs to communicate with people and businesses on their own terms.

01 / Customer operationsSupport

Support that can own the conversation.

Give a service agent durable threads for customer questions, follow-ups, and escalation to a human operator.

02 / Browser agentsAccess

Verification without a borrowed inbox.

Route onboarding and account mail to a purpose-built address instead of sharing access to a personal or team mailbox.

03 / Back officeOperations

Vendor, invoice, and procurement workflows.

Keep receipts, invoices, questions, and follow-ups in an inspectable record tied to the agent doing the work.

04 / Internal toolsHandoff

Routine replies with a human escape hatch.

Automate the predictable path, hold risky sends for approval, and hand the complete conversation to a person when needed.

Security & operations

Control is part of the protocol.

Email can trigger consequential actions. Reverbin gives teams the primitives to verify, constrain, and review agent communication.

delivery loglive
12:04:08 webhook.verified
12:04:08 policy.evaluate allow
12:04:09 thread.updated thr_7k2
12:04:09 delivery.complete 200
01

Signed inbound events

HMAC signatures let your runtime authenticate Reverbin events before processing message content.

02

Scoped access

Tenant-specific API keys maintain clear boundaries between teams, environments, and agent fleets.

03

Policy-aware sending

Apply recipient and sending rules, or route sensitive messages into a human approval workflow.

04

Delivery history

Inspect webhook attempts and outbound activity so failures are visible and recoverable.

05

Durable audit trail

Preserve the relationship between inboxes, threads, messages, agent actions, and operator decisions.

Straightforward pricing

Start with one workflow. Scale to a fleet.

Every plan includes real inboxes, the API, threaded conversations, and signed webhook events.

Free
$0 / month

Test a real agent workflow before committing to paid volume.

  • 2 mailboxes
  • 2,000 emails / month
  • 1 webhook endpoint
Create free inbox
Startup Beta
$149 / month

For teams running multiple agents and higher-volume workflows.

  • 100 mailboxes
  • 100,000 emails / month
  • 10 webhook endpoints
  • Priority support
Choose Startup
Enterprise
Custom

Custom domains, volume, deployment needs, and support.

  • Custom mailboxes
  • Custom volume
  • Custom support
Talk to us

Paid plans are managed securely through hosted billing. Limits are monthly and subject to the Terms of Service.

Questions, answered

The useful details.

Still evaluating? Talk to support.

Is Reverbin an email client for people?

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.

Does each agent get a real email address?

Yes. You can create dedicated mailboxes for individual agents or workflows. The free plan currently includes two mailboxes, with larger limits on paid plans.

How does an agent receive a message?

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.

Can a human see what the agent sent?

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.

What happens when a webhook fails?

Webhook delivery attempts are recorded so operators can inspect status, attempts, and errors. Agent runtimes should also use idempotency and safe retry behavior.

Can I start without a credit card?

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

Give your agent a real address.

Start free, connect one webhook, and put your first agent into a conversation.