Dedicated routes
Create addresses for invoices, support, reports, leads, or any other product workflow.
Mail automation
Receive, understand, and send.
Build inbound routes, turn complicated MIME messages and DMARC reports into clean webhooks, classify intent, and send transactional mail through the same API.
POST /v1/mailbox/inboundAn inbox becomes an event source your product can trust.Inbound email
From raw message to signed event.
Assign an address to a workflow. Maail receives the message, normalizes transport details, and posts a predictable payload to your endpoint.
MIME normalization
Receive text, HTML, headers, participants, and attachment metadata without writing a parser.
Signed webhooks
Verify event authenticity and handle retries idempotently with stable event identifiers.
Intent classification
Use structured rules or LLM reasoning to turn message content into an actionable category.
Spam or ham
Classify raw RFC 822 or structured content with a confidence score and reason codes.
Explicit retention
Choose workflow-specific retention instead of mixing operational mail with stateless analysis.
DMARC report analysis
Receive aggregate XML and forensic reports by email, normalize authentication results, and forward structured findings to your security workflow.
A complete flow
Email enters. Your product moves.
Transport mechanics stay behind the API. Business policy remains in your application.
Mail arrives at a route
Maail accepts SMTP delivery for the generated inbound address.
Content becomes data
Headers, bodies, attachments, and optional classification become one event.
Your webhook takes over
A signed request triggers the exact workflow your product owns.
Transactional sending
Templates without hidden behavior.
Send a fully composed message or reference a stored template. Idempotency keys make retries safe, and every accepted message receives a stable identifier.
POST
/v1/email/sendSend text, HTML, attachments, or a template with variables.
POST
/v1/email/templateCreate or update a reusable transactional template.
GET
/v1/email/message/:idRead the current delivery state for an accepted message.
POST
/v1/email/classifyClassify message content independently of inbound delivery.
Clear data boundaries
Stateless where possible. Stateful where necessary.
Standalone classification discards submitted content after returning the result. Inbound and sending retain only the operational state needed to receive, retry, and report delivery.
Artificial website examplesNo live customer traffic appears in the interface.
Signed deliveryWebhook events can be authenticated at your boundary.
German operatorXOR Ventures GmbH within the European Union.
Connect email to the product you already have.
Start with an inbound route, a transactional template, or a classifier and extend only where needed.