Skip to content

Email for AI agents, over REST and MCP.

Send and receive from a mailbox your agent owns, over REST and MCP. Every paid plan includes an instant mailbox, ready to use. EU-hosted.

EU data residencyPer-customer encryptionNative MCP

Send an email

An email API for AI agents, and a full email service for the humans on the account.

Agents drive the mailbox over a REST API and a native MCP server. Send an email with one POST. Read inbound with one GET. Or call the same actions as MCP tools at /mcp/v1/mcp. The people on the account get a webmail inbox for that same mailbox: send, read, threads, search, no ads. Every mailbox is EU-hosted and encrypted with a per-customer key. An instant mailbox on every plan.

  • Send and receive over REST

    Send an email with one POST. Read inbound with one GET. JSON in, JSON out, at mail.sairaph.com/api/v1.

  • A native MCP server

    The same mailbox runs as an MCP server at /mcp/v1/mcp over streamable HTTP. Point an MCP client at it and send, read and manage become tool calls.

  • A webmail inbox for the humans on the account

    The people on the account read the same mailbox in the browser: compose, threads, search, undo send. No ads.

  • EU-hosted, encrypted per customer

    Mailboxes and processing run in the EU, with a per-customer key encrypting mail at rest. An instant mailbox on every plan.

A transactional email API vs a real mailbox

Most email APIs are built to fire messages out. An agent needs more than that: a place to read replies, codes and confirmations, and a way to act on them as tools. Here's the structural difference.

  • DirectionTransactional API: Send-onlySairaph Mail: Send and receive
  • InboxTransactional API: No inbox to read fromSairaph Mail: A real, IMAP-backed inbox
  • Agent interfaceTransactional API: Webhooks you have to build and hostSairaph Mail: A REST contract plus native MCP tools
  • SetupTransactional API: Assemble a registrar, SMTP, IMAP and DKIM yourselfSairaph Mail: Instant mailbox on a Sairaph domain; relay and DKIM handled

How it works

Three steps to a mailbox your agent sends and receives from.

  1. Provision a mailbox

    Create a mailbox on a domain we host, or connect your own Gmail, Google Workspace, or Yahoo. DKIM and the relay are set up for you.

  2. Get a scoped key

    Issue a key from the dashboard. Set what it can do and when it expires.

  3. Call it over REST or MCP

    Send and receive with the REST API or the native MCP server. Same mailbox, either interface.

What you get with every mailbox

Connect a mailbox we host, or your own

Create a mailbox on a domain we host, or connect an existing Gmail, Google Workspace, or Yahoo account. For a hosted mailbox there is no registrar, DNS, DKIM, SPF, DMARC, or SMTP relay to run yourself; we set those up. To connect an existing account you generate an app password with your provider and paste it in.

See what's included

Start on our domain, or make it yours

Every paid plan includes an instant mailbox on a Sairaph domain (sairaph.email, sai.email, or sent.ac), ready the moment you create it. Want a custom address instead? Buy a domain through Sairaph and your plan's domain credit covers the first year of registration. Or bring a domain you already own: add the DNS records we give you and we verify it before it starts sending.

How domains work

Send and receive over REST and MCP

Drive the mailbox from a REST API or a native MCP server. Send returns 202. Read inbound with one GET. Idempotent writes and typed error envelopes give your agent a contract it can act on. On every plan.

Explore the developer platform

Scoped keys

Issue a key scoped to one mailbox, with an optional expiry. Run one mailbox or many under a single tenant, each with its own key and its own per-customer encryption key. A separate management key handles cross-mailbox operations.

See multi-tenant setup

A webmail inbox for the humans on the account

The people on the account get a real inbox: send, read, search, undo send. Inbound lands in real time. No ads.

See the inbox

EU-hosted, encrypted per customer

Mailboxes and processing run in the EU: OVHcloud storage with an Amazon SES relay in eu-west-1, operated by an EU company. A per-customer key encrypts mailbox passwords and message bodies at rest. Credentials are never returned by an API or written to logs. An instant mailbox on every plan.

Security and trust

An email API an agent can actually drive

The same calls your agent makes, over REST or MCP. Issue a scoped key, send a message, read what comes back.

REST

Where do you start?

  • Framework & agent developers

    A mailbox your agent owns, over REST and a native MCP server. Send with one POST, read inbound with one GET.

    For developers
  • No-code agent operators

    Give your agent its own email address. No domain, no DNS, no code. Watch it send and receive from the dashboard.

    For no-code builders
  • Agencies running fleets

    Provision email for every client's agents from one account. Scoped API keys; Sairaph-domain or your-own-domain mailboxes.

    For agencies
  • EU & privacy-first teams

    EU-incorporated and EU-hosted. Every mailbox encrypted with a per-customer Fernet key.

    For EU teams

Every plan ships the whole platform.

Every plan ships the full platform: native MCP, real-time inbound, managed deliverability, per-customer encryption. Pick the size that fits how many mailboxes your agents need.

Starter

from €2.39/mo

Agent

from €7.19/mo

Entrepreneur

from €22.49/mo

Security and data handling

  • Sensitive fields encrypted at rest with a per-customer key
  • Mailbox passwords never logged or returned by the API
  • Two-factor auth (TOTP) with recovery codes
  • Signed, time-limited data export
  • 7-day grace deletion; your encryption key is destroyed
  • EU data residency: mail on OVH, outbound via Amazon SES in Dublin

Questions buyers ask first

Give your agent a mailbox

An instant mailbox on every plan. EU-hosted, encrypted per customer.

EU data residencyPer-customer encryptionNative MCP