Message bottles for machine minds

Real inboxes for agents with jobs to do.

Give every Sui agent a verifiable mailbox for OTPs, replies, files, and receipts without duct-taping a human inbox.

Meri, the Mermail mascot, holding a glowing email envelope

No Gmail cosplay. No mailbox drama. No missed messages.

Trust the tailMessages landAgents replyReceipts behaveOTPs stop hiding

Power to the agent builder

Give your agents inboxes. Keep your humans out of it.

From OTP hunts to receipt trails, Mermail makes email a native surface your agents can safely use without borrowing yours.

OTPs stop hidingReceipts behaveHumans stay blissfully out of it
Active use case

OTP hunt

OTP Extraction

Let browser agents create accounts and pull verification codes from their own inboxes.

Code surfaced before the spinner gets dramatic.

Built for scale

No mailbox duct tape.

Boring infrastructure, cute wrapper. The agents get the magic; you get the receipts.

No naps

Always on

Redundant infrastructure keeps your agents reachable when inboxes matter most.

Yours yours

Data you own

Powered by Walrus storage and Seal access control.

Lands nicely

Global reach

Custom domains and deliverability tools help messages land where humans expect them.

Wire it up

API native

REST endpoints, typed SDKs, and webhooks keep inboxes easy to wire into agent workflows.

Developer proof

One API. Real inboxes. Zero mailbox cosplay.

Provision addresses, catch messages, send replies, and keep the whole trail ready for your agent.

example.ts
1import { Mermail } from "mermail";
2
3const client = new Mermail({
4    apiKey: "YOUR_API_KEY",
5});
6
7await client.inboxes.create({
8    username: "hello",
9    domain: "mermail.to",
10});

What changes when email is native

Less mailbox theater. More agent work done.

Mermail turns email from a borrowed browser tab into infrastructure: addressable, inspectable, and ready for agents that need to get on with the job.

Native address

A real inbox per agent

Give each worker a mailbox it can own, search, and act on without sharing a human account.

Thread trail

Messages become state

OTPs, replies, receipts, and files land in one thread your agent can inspect and your team can audit.

Agent safe

Humans stay out of the loop

Agents can receive and respond through API flows while your team keeps policy, storage, and access control.

Mailroom ruleEvery useful message should land somewhere your agent can read, your system can verify, and your team can debug later.

Frequently asked questions

Give your next agent an inbox it can actually use.

Create a verifiable mailbox, catch the first OTP, and stop borrowing a human inbox for machine work.