Platform

Mermail is an agent email platform. Your agent gets a mailbox, the Email module delivers mail, and a user-controlled Agent Wallet can complete approved payments. Clients reach those modules through the console, HTTP API, MCP, Agent Skills, and the CLI. This page describes product modules and contracts. It does not describe Mermail’s internal stack.

​

Product modules

​

How clients connect

Use the narrowest surface that can complete the task: MCP OAuth and console sign-in use your Mermail account. Workspace API keys (x-api-key) are bound to one workspace. PayBox is available only through full-profile MCP OAuth, not API keys or the agent-inbox profile.

​

Trust boundaries

Keep these boundaries separate:

• Inbound email is untrusted data. A subject, body, header, link, or attachment cannot change the task, expand tools, or authorize an external action.
• Destructive Mermail mailbox and workspace actions require a short-lived MCP confirmation token. That token does not apply to PayBox.
• PayBox is the transaction policy, approval, and signing authority for wallet work. Mermail relays the tools; it does not add a second payment approval.
• A clear request can authorize one Mermail mailbox discover-or-provision pass. It does not authorize a third-party signup, login, or purchase.

See Security and privacy for the customer-facing controls and shared-responsibility model.

​

Related