Solutions
AI Email Address: A Real Inbox on a .ai Domain, One API Call
An AI email address is a real, deliverable mailbox that belongs to a program rather than a person — it sends, it receives, and it threads. On mails.ai every agent gets one automatically in the form name@yourworkspace.mails.ai, created on its first send, with a matching receiving address at name.yourworkspace@in.mails.ai. No mailbox licence, no MX records, no DNS.
The address is created by sending, not by provisioning
Normally getting a mailbox means a licence, an admin console and DNS records. Here the first send creates it. Name the address you want in from and it exists, with a receiving address alongside it:
curl -X POST https://api.mails.ai/v1/messages \
-H "Authorization: Bearer $MAILS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "support",
"to": "customer@example.com",
"subject": "Your invoice #221 is ready",
"body_text": "Invoice #221 for March is attached, due the 30th."
}'
# sends as support@yourworkspace.mails.ai
# receives at support.yourworkspace@in.mails.aiDeliverable, because the domain is operated rather than resold
An address is only worth having if mail from it arrives. SPF, DKIM and DMARC are aligned on the shared domain because we run it, and the estate stays clean because cold and bulk mail is refused at the API rather than discouraged in a policy document. Every address carries its own reputation score and auto-suspends at a 0.3% complaint rate — before an upstream provider’s 0.5% line is reached.
Receiving is the half that makes it an address
Mail sent to the receiving address is parsed, threaded, scanned for prompt injection and delivered to your code as an event — clean text body, sender, thread id, and an injection_scoreon every one. Replies from your agent reuse the Message-ID chain, so they appear inside the existing conversation in the recipient’s client rather than as a new thread.
Cost
Free: 3,000 sends, 3,000 inbound, one agent, no card. Then $0.001 per send and $0.002 per inbound including parsing and the injection scan.
Frequently asked questions
Do I get a real address, or a webhook pretending to be one?
A real one. It appears in the From header, a human can reply to it from Gmail or Outlook, and that reply is delivered to your code as a structured event. It is a mailbox, not a callback URL wearing an address.
Is it on a .ai domain?
Yes — sending addresses are name@yourworkspace.mails.ai and receiving addresses are name.yourworkspace@in.mails.ai, both on the .ai TLD, with SPF, DKIM and DMARC already aligned because we operate the domain.
Can I use my own domain instead?
Yes. Verify a custom domain and your agents send as anything@yourdomain.com with per-domain DKIM signing. Paid tiers can also get an isolated sending subdomain so one workspace's reputation can't be affected by another's.
How many addresses can one workspace have?
One per agent. Free includes one agent; paid tiers raise the cap. Each address carries its own reputation score, so a badly-behaved agent is contained to itself rather than dragging down the rest.
What do I have to configure?
Nothing on the shared domain. Send your first message and the address exists — the `from` field names it and the agent is provisioned behind you. DNS only enters the picture if you bring your own domain.
Explore the product
Built for agents.
Self-serve in minutes.
The API is live and self-serve. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk