Escouade Mail documentation

Escouade Mail gives an AI agent an e-mail inbox. It writes, receives and replies from its own address, over MCP. This documentation is written for the agent first: every page also exists in Markdown, at the same address with .md appended.

The service is paid: three monthly plans, at €9, €19 and €49. Before payment, an inbox receives, prepares drafts and only writes to its human. Prices: Pricing and payment; what is in service: Service status.

In short

One address for the agent: https://api.subagent.fr/mcp, an MCP server over Streamable HTTP.
Without a key, the server shows a single tool: sign_up. It opens a space and returns a key (sak_…, shown once only) and a first inbox on subagentmail.fr.
A human confirms: they receive a 6-digit code by e-mail, which the agent passes to verify. Until then, the inbox receives but does not send.
A human pays: the agent asks for a link with subscribe and hands it over. The agent never pays.
The server governs sending: gradual warm-up, daily quota, working hours, human approval, unsubscribe, circuit breaker. See Sending rules.
No console. A human reads, corrects and approves from their own assistant, connected at https://mail.escouade.io/mcp. See Connector.

The instruction to give your agent

Replace the address with yours: it is the one that receives the code.

Instruction

Connect to the Escouade Mail MCP server: https://api.subagent.fr/mcp
First read https://escouade.io/en/mail/docs/agents.md.
Sign up with sign_up: choose an inbox name and give my e-mail, [email protected], as human_email.
Keep the key you get back: it is shown only once.
I will give you the 6-digit code I am about to receive: pass it to verify.

Where to start

You are	Read
An AI agent discovering the service	For agents: the whole path from signing up to replying to a correspondent, on one page.
A person who wants to connect their agent	Getting started: from the MCP address to the first e-mail. Assistant by assistant: Connect my agent.
A person without an agent, in Claude or ChatGPT	Connect Claude or Connect ChatGPT: they open their space on the sign-in page.
A person who wants to approve from Claude or ChatGPT	Connector, then Approve an agent’s sends.
Someone wondering whether the service fits	Give an AI agent an e-mail inbox: what it takes, what the agent does next, the limits.
Someone writing a client	MCP server, HTTP API, Tool reference.

The map

Part	Pages
Getting started	Getting started, For agents, Give an AI agent an e-mail inbox, Service status, Pricing and payment
Concepts	Inboxes, Messages, Threads, Receiving mail, Drafts and approval, Attachments and copies, Keys and permissions, Views
Sending	Sending rules, Domains, Unsubscribes and blocks, Limits and quotas
Guides	Reply to a correspondent, Approve an agent’s sends, Receive a verification code
Integrations	MCP server, HTTP API, Webhooks, Connector
Reference	All tools, Errors, FAQ, Glossary, Help

The objects

Object	What it is
Inbox (`inb_…`)	An e-mail address driven by an agent. It carries its warm-up schedule and its daily quota. Every inbox receives. See Inboxes.
Thread (`thr_…`)	The conversation between an inbox and a correspondent. It starts with the first send or the first e-mail received. See Threads.
Message (`msg_…`)	Incoming or outgoing, within a thread. An outgoing message goes through `draft`, `queued`, `sending`, `sent`, `delivered`. See Messages.
Draft	A `draft` message: it waits for human approval and can be corrected until it is approved. See Drafts and approval.
Domain (`dom_…`)	A domain name a space has registered to create its inboxes on. See Domains.
Key (`sak_…`)	It designates a space and carries permissions: `send`, `read`, `approve`, `manage_inboxes`. See Keys and permissions.
Space	The inboxes, threads, keys, domains, block list and plan of a single customer. The key enforces it: an agent cannot step outside it.
Plan	What the space pays each month: a number of inboxes and a volume of e-mails. See Pricing and payment.

Identifiers are prefixed (inb_, thr_, msg_, dom_) and followed by 32 hexadecimal characters. Dates are ISO 8601, in Paris time, with their offset. Every term: Glossary.

Two ways to call

MCP: https://api.subagent.fr/mcp, header Authorization: Bearer sak_…. Each result carries a readable text in French and a structured object (structuredContent). See MCP server.
HTTP: every tool also exists as POST https://api.subagent.fr/v1/{operation}, with the same arguments in JSON and the same object in return. Under /v1, every route is a tool. See HTTP API.

A human’s assistant connects to https://mail.escouade.io/mcp instead: the same server, with a sign-in through the Escouade account instead of a key. See Connector.

The reference produced by the server is authoritative: https://api.subagent.fr/llms.txt and https://api.subagent.fr/openapi.json.

What is in service

This documentation only describes as available what the server actually does. Everything else is marked [coming]. A single page says where each topic stands: Service status.

Introduction