Product | AgentMail

product

Provision real inboxes via API and give them the scale they need without running into bottlenecks introduced by Gmail.

0101110111110100000100101010001101101110110010 0100000011100000000110111011000010011110000111 0011010001001001100101101111100100001000110111 1111101111010000100100111001001100011000101001 0100100011000010100110010001010110111111000000 0110001101000100100111100111010010100110011010 0110000001101100001010000010000101000110101100 0001100011100111110100010111101010100111010111 0101010101101101001101000110000011101010110110 1100111100100100101010010010111001110011111001 0010101111110100000010011110111111101111000001 1100011011101101010111110001001000001101010001 1000010101010101010111010111010101011111010101 0111110110001010100000110000011010111011011110 0110101010101000000010000101010000101010001110 0010011010001010011010010010100111100001000110 0111000110100110010010110000110000111100101110 1000111110110010111001110011110101011110100110 1001100110000111000110000000101100111101101000 1000000000101010010110111000011001001000100101 0101001010011001101010000001010101010110010010 0011011001101100010111100001001101

Persistent conversations

Monday
Agent requests a quote.
Tuesday
Run ends.
Thursday
Vendor replies with a PDF.
Event
Webhook notifies your app.
Agent
New run retrieves the thread.
Agent
Agent replies.

Replies and attachments stay in one thread, ready for your agent’s next run.

THE OLD EMAIL STACK

The inbox is now an API resource you can do CRUD on. No more having your agents click through UI via CUA.

Inbox

12 new

Gmail

Visa Debit

11:29

Payment received

Re: Project update

10:14

3 new messages

Design review

Yesterday

2 attachments

Access request

July 3

Permission needed

Research complete

12:42

Report is ready

Re: Customer inquiry

11:08

2 new messages

Invoice attached

9:36

1 attachment

Follow-up required

July 4

Reply requested

Task completed

2:17

Results are ready

Re: Account review

1:03

4 new messages

Weekly summary

Yesterday

1 attachment

Meeting request

July 2

Response needed

Sent

MessageAPILogs

1{
2  "to": "user@company.com",
3  "from": "noreply@agentmail.com",
4  "subject": "Your report is ready",
5  "body": "Hi there, ...",
6  "headers": {}
7}

product

Scale to more inboxes, more email per inbox, or both.

Start for free

Diagram: one customer fans out to four agents, and every agent has its own inbox

Diagram: one customer reaches a single inbox that fans out to four emails

A digital passport to sign up, connect, and interact online.

See what you can build

An agent signs in with email, verifies its identity with a 2FA code sent to agent@mail.to and accesses an Amazon account

Subscribe to incoming-email events and let your application start a run when a message arrives. Your agent can read the request, retrieve attachments, and reply through the API.

See what you can build