Mails.ai gives a software agent its own working email address, a way to send from it, and a way to read what comes back. Your agent sends a booking confirmation from [email protected], the customer replies, and that reply arrives at your code as a structured event — sender, subject, body, intent, and a prompt-injection score — instead of raw MIME you have to parse.
A real address per agent. sarah@ and notify@ are separate identities with separate reputation, not one shared mailbox.
A send API. One POST, one Authorization header. No SMTP.
Inbound as typed events. reply.received carries the parsed body plus intent, entities, urgency and an injection_score.
Deliverability handled underneath. Pool routing, suppression, per-agent reputation and complaint monitoring run on every send.
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 inside an existing thread, 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.
