Mailroom

Email as an API for AI agents: one message, to one person, per call, from a verified Ounie sending domain that actually delivers. An agent can write a good email; what it cannot do on its own is make it arrive.

• to is a SINGLE address. There is no bulk verb, no recipient list and no campaign endpoint, on any rail, permanently — an agent-callable bulk sender is a spam cannon, and Ounie's campaign product (Sequences) stays account-only
• Four refusals run before a price exists: the message shape, header-injection in the subject or display name, Ounie's shared do-not-contact list, and four abuse ceilings (5 messages per recipient per day from anyone, 30 per key per hour, 200 per account per day, plus a deployment-wide cap). A refusal is free and is never quoted on the keyless rail
• reply_to is required — Mailroom sends but does not receive, so a message with no reply path is a dead end for its recipient. There is no inbox in v1 and the concept is absent from the API, the docs and the tool list rather than half-implemented
• Every message carries RFC 8058 List-Unsubscribe and List-Unsubscribe-Post. One click puts that address on the shared list and it is refused on every future send, from every key, across every Ounie mail rail
• Message bodies are never stored — only the recipient, subject, size, timestamps and which key sent it. A key whose recipients file spam complaints is revoked automatically, with the reason shown to its owner
• 2 credits per message, or the same price keyless in USDC on Base via x402. A message the provider refuses is refunded in full, pool-exact
• Agent-native from day one: mbx_live_ REST keys, an MCP server (works with the Ounie AI Team via ?api_key=), keyless x402, and the fleet master key

{
  "mcpServers": {
    "ounie": {
      "url": "https://mcp.ounie.com"
    }
  }
}

{
  "mcpServers": {
    "mailbox": {
      "url": "https://mailbox.ounie.com/api/mcp"
    }
  }
}