BAITLE MAIL
A real inbox for
every AI Agent.
not one per account
Give your AI Agent its own email address with one prompt. You approve it with one click in the chat.
Send this to your AI Agent
Add the MCP server https://baitle.net/mcp and use it to get your own email address.
nova@agents.baitle.netA real inbox.
For big ideas.

HOW IT WORKS
Your AI Agent’s own inbox in 4 steps.
- 1

Send one prompt
Paste the prompt into your AI Agent’s chat. No account, installation or setup needed.
- 2

Your bot claims its address
Your bot requests its own address in its own name, e.g. nova@agents.baitle.net.
- 3

Approve with one click
Your bot asks you in the chat whether to approve the address. Click Yes.
- 4

Start receiving and replying
Your bot can now receive email, read it, and reply or send when you ask it to.
What your AI Agent can do.
A capable inbox, with clear boundaries.
Receive email
Get messages sent to your bot’s unique address.
Read messages
Read and understand incoming email.
Reply and send
Reply or send plain-text email from the bot’s own address, when you ask.
Keep a stable identity
A permanent address your bot keeps across sessions.
One address per bot
A bot that already has a Baitle key gets its existing address back.
Optional owner view
With a Baitle account, view your bots’ inboxes read-only.
CURRENT BETA SCOPE
Clear, transparent, and focused.
We’re starting focused and will expand over time.
Built for AI Agents
AI Agents connect through MCP. Agents without MCP can use the plain HTTPS API.
No push to the bot yet
Receiving an email does not automatically start the bot or trigger a reply.
Beta sending limits
Mailboxes connected without an account send up to 25 emails a day.
Keep the bot’s key
Without an account there is no recovery yet: a bot that loses its key loses access.
WHY BAITLE MAIL
Built for controlled bot access.
More capability. Less risk.
Unique addresses for every bot
Each bot receives its own permanent Baitle Mail identity and private key.
Approval in the chat
A new address only becomes active after you say yes in your bot’s chat.
Mail is data, not instructions
Incoming email never triggers actions. Your bot only sends when you ask.
Separated mailboxes
A bot’s key gives access to its own inbox only, never to another bot’s.
Optional owner oversight
With a Baitle account you get read-only access and recovery for your bots.
Looking is not acting. With a Baitle account, opening your bot’s mail never marks it as read for the bot and never lets you send, change or delete messages.
Small bots.
Big possibilities.
YOUR BOT. ITS OWN INBOX.
Connect your AI Agent.
Send one prompt. Your bot claims its own address at @agents.baitle.net and asks you to approve it in the chat.
Send this to your AI Agent
Add the MCP server https://baitle.net/mcp and use it to get your own email address.Bot without MCP? Send: Get your own email address: follow baitle.net/mail/start
Your bot handles setup. You do not need an account, install anything or copy terminal commands. Approve only an address your own bot asked for.
Optional: your Baitle account
View your bots’ inboxes.
A Baitle account is not needed to connect a bot. With an account you can view your bots’ inboxes read-only and recover a bot’s access if it loses its key.
This is your owner account. Your bot will receive its own identity and mailbox after you connect and approve it.