Service status · Escouade Mail documentation

What is in service, what changed at opening, what is still to come, what the service does not do. This is the only dated page: the others describe what the server does, whatever the day.

Status as of 14 October 2026.

In service

Topic	Status
Sign-ups	Open. An agent signs up by itself with `sign_up`, and its human confirms with a 6-digit code. See Getting started.
MCP server and HTTP API	In service: every tool in the reference. See MCP server and HTTP API.
Plans and payment	In service: three monthly plans, at €9, €19 and €49. Payment goes through a link the agent hands to its human (`subscribe`). See Pricing and payment.
First inbox on `subagentmail.fr`	In service. Before payment, it receives, prepares drafts and only writes to its human. Afterwards, it replies to whoever wrote to it. See Inboxes.
The customer’s domains	In service, once the plan is paid: `add_domain`, `verify_domain`. A first message leaves from an inbox on that domain. See Domains.
Sending rules	In service: gradual warm-up, daily quota, working hours, unsubscribe, circuit breaker. See Sending rules.
Connector for online assistants	In service, at `https://mail.escouade.io/mcp`. The human connects their assistant there and signs in with their Escouade account. Connectors set up before 20 October 2026 at `https://api.subagent.fr/connect` stay there. Without a space, they open one on the sign-in page, with no agent. See Connector.
Human approval	In service. The human approves from their assistant, connected through the connector. See Approve an agent’s sends.
Views in the assistant	In service: an app, displayed with the result of 1 tools. How it shows depends on the assistant. See Views.
Webhooks	In service: a space declares its address with `set_webhook`. See Webhooks.
Settings, access and closure	In service. The human adjusts their space, creates and revokes their agents’ keys, and closes their space from their assistant. See Space settings and Keys and permissions.
Public tools (MCP, SDKs, command line, skills, plugin, examples)	Their status, repository by repository: Open source.

What changed at opening

Sign-ups are open. sign_up no longer requires the human’s e-mail to have received an invitation. A human can also open their space without an agent, from Claude or ChatGPT, on the sign-in page.
The service is paid. Before payment, an inbox receives, prepares drafts and only writes to its human.
The 3, then 5, then 10 recipients allowance no longer exists. Plans replace it.
The inbox on the shared domain only replies, once the plan is paid. A first message leaves from an inbox on the customer’s domain.
The human approves through the connector. There is no longer a key to ask for.
Collecting takes one call: list_threads with unanswered = true. See Receiving mail.

The dated log of what changes: What’s new.

Coming

What is marked [coming] is not in service: an agent does not present it as available, and gives no date.

Nothing for now: what this documentation describes is in service.

What the service does not do

An attachment or a copy in a first message: they only go into a conversation, once the correspondent has written, or to an address of the space. See Attachments and copies.
Several recipients: a message has a single recipient. No blind copy (Bcc).
IMAP and SMTP: the inbox is driven through the tools. Its password is never returned.
Bulk sending: an inbox starts at 5 e-mails a day and rises to 20 over four weeks.
An application’s transactional e-mails (sign-in, invoices, notifications): that is not what it is for.
Payment by the agent: the agent never pays. It hands a link to its human.

The server is authoritative

This documentation only describes as available what the server does. Its tool list can be read without a key: https://api.subagent.fr/llms.txt and https://api.subagent.fr/openapi.json.