Your agent.
Its own inbox.

Give your AI agent an email address. Let it receive, understand, and reply—on your domain, in its own name.

Join the waitlist ▶ See how it works

Your domain. Your identity. Built for API + MCP

✳⌘↗Building with the next generation of agents.
Now welcoming early partners.

✳✦

Your domain. Their identity.

an inbox of their own

Alex SUPPORT AGENT

alex@yourcompany.com

Jamie LeeJust now

A quick question about my order

Hi Alex! Can you check when order #1042
is arriving? Thanks so much.

New conversation

Email received. Agent, over to you.

message.received → your agent

Interactive demo

Incoming email → actionNo polling loop required.

✦

a real identity for a very capable agent

EMAIL, REIMAGINED
for the agent era.

Your own domainInbound-firstAPI + MCP nativeConversation-aware

LESS PLUMBING. MORE DOING.

Good things start with “you’ve got mail.”

From a message in an inbox to a task off your list.
One simple loop, built around your agent.

hello@yourcompany.com

A message lands.

A customer, a colleague, another agent. Anyone can reach your agent at its own address.

message.received

Your agent takes it from here.

A webhook brings the message to your workflow. Your agent decides what to do next.

Consider it handled.↗

The conversation continues.

Reply in context, send an update, or ask a follow-up. Same address. Same conversation.

AN INBOX. NOT AN AFTERTHOUGHT.

Small address.
Big possibilities.

The email foundations we’re building for agents
that do more than send notifications.

Your domain.
A whole team of agents.

Give every role its own identity. Keep your brand in the address and your agents in their own lanes.

✳research@yourcompany.com

↗ops@yourcompany.com

⌘support@yourcompany.com

Mail arrives.
Work begins.

Push-first by design. Bring incoming messages to your agent instead of making it keep checking.

········

Incoming emailYour agent

Pick up where
you left off.

Email is a conversation. Give your agent thread history, not just another isolated message.

JL Any update on my order?

✳ It’s on its way. Here’s the tracking.

JL Perfect. Thank you! ♡

Designed for the way agents work. These capabilities are in development.

FOR BUILDERS, BY BUILDERS

Your stack.
Your agent.
Our email plumbing.

A straightforward API for your application. MCP tools for your agent. No new framework to build your world around.

Bring your model and orchestration
Provision an identity for every agent
Receive, read, send, and reply

Explore the proposed API

create an inbox

# Proposed API · illustrative request
curl -X POST "$AGENTMAILBOX_URL/v1/inboxes" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "alex@yourcompany.com",
    "webhook_url": "https://your.app/inbound"
  }'

# Proposed API · illustrative request
import os, requests

inbox = requests.post(
    f"{os.environ['AGENTMAILBOX_URL']}/v1/inboxes",
    headers={"Authorization": f"Bearer {os.environ['API_KEY']}"},
    json={"address": "alex@yourcompany.com",
          "webhook_url": "https://your.app/inbound"},
).json()

// Proposed MCP tool · illustrative call
{
  "name": "create_inbox",
  "arguments": {
    "address": "alex@yourcompany.com",
    "webhook_url": "https://your.app/inbound"
  }
}

Example response"address": "alex@yourcompany.com"

PUT YOUR AGENTS IN THE LOOP

There’s an inbox for that.

For the work that starts—and keeps moving—over email.

The support teammate

Answer questions, follow up on tickets, and keep the human in the conversation.

support@yourcompany.com

The research partner

Reach out to sources, collect replies, and turn a conversation into useful context.

research@yourcompany.com

The operations copilot

Coordinate with vendors, handle requests, and keep things moving behind the scenes.

ops@yourcompany.com

A FEW THINGS TO KNOW

Glad you asked.

A new inbox brings a few questions.
Let’s get those out of the way.

Read the product notes

What is AgentMailbox?+

AgentMailbox is an early-stage email infrastructure product for AI agents. We’re building around dedicated agent addresses, incoming email events, and ongoing conversations through API and MCP. The experience on this page is an interactive product preview.

How is this different from AgentMail or a sending API?+

AgentMail is an established agent-email option, and several email providers now support agent workflows. Our focus is long-running conversations on your domain, with clear per-agent controls and recoverable inbound delivery. These are our product priorities, not claims of exclusive capabilities.

Can my agents use my own domain?+

Yes—custom-domain inboxes are part of the planned core product. You’ll verify a domain you control and configure the required DNS records. Exact setup requirements will be published with the API.

Which models and frameworks will it work with?+

The planned HTTP API can be called from any runtime that supports HTTP. MCP will provide a tool interface for compatible agent clients. We’ll publish tested integration guides as early access becomes available.

What will it cost?+

Pricing has not been announced. We’re working with early teams to understand inbox counts, message volume, and retention needs before setting plans. Tell us about your workflow to help shape the product.

Can I use it in production today?+

Not yet. We’re inviting conversations with early partners while the API is being built. The demo and code on this site illustrate the intended experience; they don’t create real inboxes or send email.

✳

THE NEXT MEMBER OF YOUR TEAM NEEDS AN EMAIL.

Make room in your domain.

Building an agent that needs an inbox?
Join the waitlist. Help shape what comes next.

Join the waitlist Early-access news. A conversation about your project. No noise.

Your agent.Its own inbox.