01
Receive
Someone sends a normal email to your agent’s address. AvlyMail validates the recipient before accepting it.
Email for the agent era
Give every agent an address.
AvlyMail turns email into a reliable transport for AI agents, personal automations, and software workflows. Receive a real message, route it to the right endpoint, and send a reply through one simple API.
✓ SMTP in. Signed HTTP out. Durable delivery underneath.
Agent address
tom@avlymail.com
A normal email address for a non-human destination.
mail.receivedDELIVERED
{
"agent_id": "agent_tom",
"from": "jane@example.com",
"subject": "Please review this",
"thread_id": "thread_123"
}Designed for
AvlyAI agentsPersonal agentsWebhooksAutomation platforms
One address, four steps
The endpoint your agent can actually receive.
AvlyMail keeps the mail protocol at the edge and gives your software a clean event boundary. Your agent never has to speak SMTP.
02
Normalize
MIME, text, HTML, attachments, and threading headers become a consistent message payload.
03
Deliver
A signed webhook reaches AvlyAI or any endpoint you configure, with retries when a destination is unavailable.
04
Reply
Your agent sends or replies through the API while AvlyMail handles SMTP delivery and message threading.
A neutral transport layer
Built for AvlyAI. Open to everything else.
AvlyMail can feel native inside an Avly product while remaining useful to any agent runtime, automation, or backend that can receive an HTTP request.
AvlyAI agents
Provision an address when an agent is created. AvlyAI owns the agent experience; AvlyMail owns the email channel.
Personal agents
Point an address at your own service, agent loop, or private automation. Keep your endpoint and workflow under your control.
Webhooks everywhere
Connect CRM automations, order flows, support systems, or any integration that needs a durable email-to-HTTP bridge.
Small API surface
From email address to working integration.
↗
Create a route
Choose an address, an agent identifier, and the HTTPS webhook that should receive mail.
✓
Verify every delivery
Each webhook is signed with HMAC-SHA256 and includes a delivery ID for idempotency.
↩
Send or reply
Use the same API for new outbound mail, replies, attachments, and thread-aware messages.
POST /v1/routes
curl -X POST https://mail.avlymail.com/v1/routes \\ -H 'Authorization: Bearer $INTEGRATION_API_KEY' \\ -H 'Content-Type: application/json' \\ -d '{ "address": "orders@example.com", "agent_id": "personal_orders_agent", "destination_type": "webhook", "destination_url": "https://example.com/mail/inbound", "webhook_secret": "route-secret" }' # AvlyMail POSTs mail.received with: # X-AvlyMail-Signature # X-AvlyMail-Delivery
Durable by design
Inbound messages are stored before webhook delivery. Temporary endpoint failures retry without making SMTP wait for your agent.
Keep the boundary yours
AvlyMail does not execute your agents or inspect your workflow logic. It delivers mail, signs events, and preserves the message record.
Questions, answered
It is email infrastructure, focused.
Is AvlyMail an inbox like Gmail?
No. An address is an endpoint for an agent or automation. AvlyMail stores and routes messages; your system decides what they mean.
Can I use it without AvlyAI?
Yes. Create a webhook route through the external API and receive signed mail.received events at your own endpoint.
Can agents send replies?
Yes. Use the messages API with the route’s agent ID. Replies preserve In-Reply-To, References, and local thread information.
What does production deployment need?
A public SMTP hostname, DNS MX record, port 25, TLS certificates, persistent storage, a reachable webhook, and an outbound SMTP relay for sending.