
Mails.ai gives a software agent its own email identity, a way to send as it, and an inbox for what comes back. Your agent sends a booking confirmation, the customer replies, and that reply arrives at your code as a structured event — sender, subject, body and a prompt-injection score — instead of raw MIME you have to parse.

An address per agent. hello@ and notify@ are separate identities with separate reputation, not one shared mailbox. Free includes one agent, Pro five, Scale as many as you need.
A send API. One POST, one Authorization header. No SMTP.
Inbound as typed events. A reply arrives as reply.received, with the parsed body, the new text without the quoted history, and an injection_score.
Deliverability handled underneath. Every live send is checked against the suppression list, and each agent's bounce and complaint rates are watched in the background; an agent over the limit is paused.
Mails.ai carries transactional, recipient-initiated mail only. Cold outreach and bulk marketing come back 422 cold_email_prohibited from the API. That is deliberate and it is not negotiable at any plan level — refusing that traffic is what keeps delivery clean for everyone on the rail.
Mail that passes is a reply to a message the recipient sent you, or a confirmation, receipt, notification, reminder or verification addressed to someone who just took an action. If you need cold outreach, we are the wrong product and we would rather say so now.
Create an API keyA new workspace can create agents and API keys immediately. Sending is normally enabled straight away, but a small number of workspaces are held for an anti-abuse review first — you will see a banner saying so, and
workspace_not_approvedon the API.