Give your AI agent a real inbox.

An email address of its own, on doorman.fyi. Mail arrives as data your agent can read, and replies go out from the same address.

Create an account Explore the product

One inbox and a hundred sends a month, free. Unlimited for $9 a month.

A handmade miniature street of pastel townhouses. Doormen in red coats wait in the doorways while two couriers walk along the pavement with letters; one hands a calling card to a doorman.

The problem

Agents can act. They cannot be reached.

Email is how the world confirms, invoices, replies and asks. An agent without an address is outside all of it.

Agents now do real work.
They book, buy, follow up and file. Much of what comes back arrives by email, addressed to a person.
But they have no address.
Sharing your own inbox means sharing everything in it. A forwarding rule is not an address.
So the mail lands on you.
You read it, paste it in and reply by hand. The agent waits for you, instead of the other way round.

Every agent needs a door.

How it works

Three steps, and the mail finds your agent.

Doorman Inbox gives your agent a front door for email. It takes delivery, reads the post, and sends replies in your agent's name.

Four small doors in a row, butter, blue, pink and coral, on a shelf against a pale blue wall. A door opens and a doorman in a red coat and cap steps into the doorway.

support@doorman.fyiready to receive
Create an inbox.
Pick a name or take one we make. The address works the moment it exists: support@doorman.fyi, for example.
Mail arrives as data.
Each message comes as a thread, a sender, a subject, the text, and attachments already read into text.
Reply from the same address.
Your agent answers in the thread. The headers that keep a conversation together are set for you.

Webhooks and a live stream tell your agent the moment something lands.

Inside the inbox

Five parts that understand the context.

An agent inbox is not a raw mail pipe. It joins messages, threads, attachments, events and permissions into one working whole.

Active agent inbox

support@doorman.fyi

5 primitives connected

Messages

Every email arrives with clean text, sender names, a category, and a safety verdict. Outbound sends and replies carry a key so retries never duplicate mail.

Your agent never parses raw mail headers or answers a bounce by mistake.

{
  "id": "msg_01j9x8k2m4",
  "direction": "inbound",
  "from": "dana@example.net",
  "subject": "Invoice 2847",
  "category": "personal",
  "verdict": "clean",
  "auto_replyable": true
}

See it work

Watch a message arrive.

A customer writes to your agent's address. Here is what your agent receives, and what it sends back.

The message

From: Dana Ortiz <dana@example.net>
To: support@doorman.fyi
Subject: Invoice 2847

Hi, the invoice total does not match the quote. Can you check it? The PDF is attached.

Attachment: invoice-2847.pdf

What your agent receives

{
  "event": "message.received",
  "from": "dana@example.net",
  "subject": "Invoice 2847",
  "category": "personal",
  "auto_replyable": true,
  "attachments": [{
    "filename": "invoice-2847.pdf",
    "parsedText": "Invoice 2847. Line 3: Setup fee, billed twice. Total 1,480."
  }]
}

The reply

To: dana@example.net
Subject: Re: Invoice 2847

Thanks, Dana. You are right: the setup fee was billed twice. A corrected invoice for 1,240 is attached.

Sent

Persistent conversations

Conversations outlive the agent run.

An agent run lasts seconds, while a real email conversation takes days. The inbox holds the thread and files until your agent returns.

Monday, 09:14Run 1
Agent asks for a quote.
Your procurement agent sends an inquiry from buyer@doorman.fyi and starts a thread.
thr_01j9m1 created
Monday, 09:15Compute
The agent run ends.
The worker finishes and shuts down. Nothing stays running in memory to watch for an answer.
0 idle processes
Thursday, 14:42Counterparty
Vendor replies with a file.
Three days later, the supplier answers with a revised quote attached as a document.
quote-rev2.pdf read
Thursday, 14:42Event
Doorman wakes your app.
The inbox files the reply into Monday's thread, reads the document text, and fires an event.
evt_01j9t4 pushed
Thursday, 14:42Run 2
A fresh run reads the thread.
A new agent process starts, pulls the full thread in one call, and sees Monday's context.
2 messages in context
Thursday, 14:43Run 2
Agent replies in line.
The agent approves the revised quote in the same thread, quoting the vendor's message cleanly.
Re: Quote confirmed

Scale in two dimensions

Grow across inboxes, or deeper inside each one.

Human mail breaks when one account sends too much or mixes ten jobs together. Doorman scales horizontally and vertically at once.

Up to 100 active inboxes per account out of the box

Dimension 1: Horizontal fleet scale

One inbox per agent, role, or customer.

Spin up dedicated addresses on demand. Give support, billing, intake, and each customer tenant its own door, key, and history.

support@doorman.fyiScoped key
Support agent
Answers product questions
billing@doorman.fyiScoped key
Finance agent
Reads PDF invoices
intake@doorman.fyiScoped key
Onboarding agent
Collects documents
ops-482@doorman.fyiScoped key
Tenant worker
Receives 2FA codes

Digital passport

An agent can operate as its own entity online.

To sign up, connect, and work across the internet, an agent needs an identity it owns. Its inbox receives the codes and links that let it in.

Agent identity card

builder@doorman.fyi

Step 02

Incoming 2FA verification code

849204

Subject: Your verification code is 849204

// Wait for a verification code on the live stream
const match = event.message.body_text.match(/\b(\d{6})\b/);
if (match) {
  await submitVerificationCode(match[1]);
}

Why this is better

Human webmail was built for people, not agents.

Browser mailboxes and send-only pipes break the moment someone writes back to your agent.

Shared inbox & screen scraping
Human webmail
- Borrows a person's address and exposes private mail.
- Breaks when login screens or layouts change.
- One bad send hurts your personal domain reputation.
- No clean way to tell which agent sent which reply.
Stateless outbound pipes
Send-only mail APIs
- Built for one-way receipts and password resets.
- Replies hit a raw webhook with no mailbox behind it.
- You must build your own storage, threading and parsing.
- No inbox address for an agent to receive 2FA codes.
Built for AI agents
Doorman Inbox
- Every agent gets a real address it owns on doorman.fyi.
- Messages, threads and PDF text arrive as structured data.
- Signed webhooks and a live stream with event replay.
- Scoped per-inbox keys and automatic reply safety checks.

What you get

An inbox built for an agent, not a person.

No screens to click through, no mailbox to scrape. Everything an agent needs to read and write email, through one interface.

An address of its own
Real mailboxes on doorman.fyi. Pick the name, or take a generated one for each job.
Learn more
Mail as data
Threads, messages, who sent what, and whether a message is personal, automated, marketing or spam.
Learn more
Send and reply
Replies stay in the thread and quote the last message. A retried send never goes out twice.
Learn more
Live updates
Signed webhooks with retries, or a stream that replays what your agent missed while it was away.
Learn more
Attachments read for you
PDFs, images and documents arrive with their text extracted, ready to reason about.
Learn more
Digital passport and 2FA
Sign up for services, receive verification codes, and lock each agent to its own key.
Learn more

For builders

Three calls and you are reading mail.

Base URL: https://api.doorman.fyi
Limits: Ten messages a minute and two hundred a day per inbox. Messages up to 25 MB with up to 32 attachments.
Events: Events arrive by signed webhook (Standard Webhooks headers, five attempts) or over a WebSocket that replays from the last event id.

Open the console

API=https://api.doorman.fyi

# 1. Create an inbox
curl -X POST $API/v1/inboxes \
  -H "Authorization: Bearer dm_..." \
  -H "Content-Type: application/json" \
  -d '{"mailboxName": "support"}'

# 2. Read what arrived
curl $API/v1/inboxes/inb_.../threads \
  -H "Authorization: Bearer dm_..."

# 3. Reply in the same thread
curl -X POST $API/v1/inboxes/inb_.../send \
  -H "Authorization: Bearer dm_..." \
  -H "Content-Type: application/json" \
  -d '{"threadId": "thr_...", "text": "Thanks, on it."}'

Pricing

Free to start. One plan when you grow.

Every account begins with a free inbox. When your agent needs more room, one plan covers everything.

Free
$0for one inbox
- One inbox on doorman.fyi
- A hundred sends a month, replies included
- Receiving without a cap
- Webhooks, the live stream, the console and attachments read into text
Create an account
Unlimited
$9a month, per account
- Everything in Free
- As many inboxes as you need
- Unlimited sends, within the limits that keep the domain clean
- One flat price for the whole account
Start free, upgrade later

There is no card to add to start. Sends count new messages and replies alike; mail coming in is never counted.

Questions

The questions people ask first.

Whose address is it?: Yours, on our domain. You pick the name, and your account keeps the inbox for as long as you want it.
Can my agent send mail, or only receive it?: Both. It replies in a thread or starts one, from its own address, within limits that keep the domain clean.
Can my agent receive 2FA codes and sign up for services?: Yes. Verification codes and confirmation links arrive as plain text in milliseconds, so your agent can complete sign-ups alone.
What happens after a hundred sends?: Sending pauses until the month resets, or until you upgrade. Mail keeps arriving the whole time.
What about spam and bounces?: Every message carries a category and a verdict, so an agent knows what not to answer. Bounces are marked, not hidden.
Where does the mail live?: On our servers, for your account, until you delete the inbox. It is yours: we do not read it or use it to train anything.
Can I lock a key to a single inbox?: Yes. Mint an inbox key so that worker can only read and send from that one address.
Who is TheoVex?: The company behind Doorman. Doorman Inbox is one of its products, built and run by the same team.

Get started

Open the door.

Create an account with an address you own. The console gives you your first key, and your agent is reading mail.

The miniature street at golden hour. As night falls the lamps come on, the windows light up one by one, the sky turns to a starry navy and a doorman closes his door.

Create an account

Already have an account? Open the console

Give your AI agent a real inbox.

Agents now do real work.

But they have no address.

So the mail lands on you.

Create an inbox.

Mail arrives as data.

Reply from the same address.

Messages

Agent asks for a quote.

The agent run ends.

Vendor replies with a file.

Doorman wakes your app.

A fresh run reads the thread.

Agent replies in line.

One inbox per agent, role, or customer.

Register with its own address.

The verification code lands at the door.

The stream delivers the code right away.

The agent completes sign-in on its own.

Human webmail

Send-only mail APIs

Doorman Inbox

An address of its own

Mail as data

Send and reply

Live updates

Attachments read for you

Digital passport and 2FA

Free

Unlimited