Sairaph Mail for AI Agents

What it is

A real two-way email mailbox an agent owns and operates: send messages, receive and read inbound (including verification codes and replies), over REST or MCP. Not a send-only transactional API; not a borrowed human account.

Agent surface (canonical facts)

• Product: real, EU-resident, two-way email mailboxes for AI agents.
• REST API base: https://mail.sairaph.com/api/v1
• Native MCP server: https://mail.sairaph.com/mcp/v1/mcp (transport: streamable-HTTP; auth: mailbox Bearer key)
• Docs: https://mail.sairaph.com/docs
• No language SDK package and no `/messages` endpoint - the surface is plain REST plus the open MCP protocol.

Capabilities

• Send: POST /api/v1/mailboxes/{mailbox_id}/outbound. An Idempotency-Key header is required, so a retried request can never send the same email twice. Returns 202 with { object: "message", id: "msg_…", status: "queued" }.
• Receive / read inbound: GET /api/v1/mailboxes/{mailbox_id}/messages?direction=inbound. Returns a Stripe-style list envelope { object: "list", data: [...], has_more, next_cursor, url }; paginate with ?cursor=.
• Live read (blocking on a code): add &live=true for an on-demand fetch with a cached fallback; rows discriminate cached_message vs. live_message.
• MCP tools: the mailbox's send and read/list actions surface as MCP tools to any MCP-capable runtime.

Authentication & keys

• Per-mailbox keys (sm_live_…) with roles read / read_write, used as a Bearer token on both REST and MCP.
• Tenant management keys (sm_mgmt_…) for cross-mailbox operations.
• Keys are issued from the dashboard only - issuance is deliberately not agent-callable, so a leaked key can never mint or revoke another. Keys can carry an optional expiry.

Errors & rate limits

• Errors use a Stripe-shaped envelope: { error: { type, code, message, param } }.
• Over-limit responses on the agent API return 429 with a Retry-After header.

Security & residency

• EU-resident by default, on every plan: mailbox storage on OVHcloud (EU); outbound relay via Amazon SES in eu-west-1 (Dublin). Operated by an EU-incorporated company (WELLDONE, Poland).
• Encryption at rest: mailbox credentials and message bodies are sealed with a dedicated per-customer key using authenticated encryption (Fernet - AES-128-CBC + HMAC-SHA256); per-customer keys are wrapped by a rotating master key.
• Credentials are never returned by any API and never written to logs.
• Honest residency nuance: the SES relay runs in eu-west-1 but on AWS, and once delivered, mail travels to the recipient's server anywhere - we never claim "your email never leaves the EU."

Quick connect

Send (REST):

curl https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/outbound \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["agent@acme.dev"],
    "subject": "Your verification code",
    "body_text": "Reply with APPROVE to continue."
  }'

Read inbound (REST):

# Read inbound from cache, or live=true for an on-demand fetch.
curl "https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/messages?direction=inbound&live=true" \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY"

Connect MCP:

https://mail.sairaph.com/mcp/v1/mcp
Authorization: Bearer $SAIRAPH_MAIL_KEY

Learn more

• Email for AI agents - the 2026 guide
• MCP email server
• Inbound email API
• REST API reference · MCP setup
• Docs: https://mail.sairaph.com/docs