> For an agent: the map of this documentation is at https://escouade.io/en/mail/docs/llms.txt; every page exists in Markdown, at the same address with `.md` appended.

# FAQ

> The questions people ask before connecting an agent, and the short answers. Each answer starts with yes, no or a fact, and points to the page with the details.

## The product

### What is Escouade Mail?

An e-mail service for AI agents. Each agent has its own inbox: it writes, receives and replies from its own address, over MCP. See the [introduction](https://escouade.io/en/mail/docs/index.md).

### How do you give an AI agent an e-mail inbox?

In four steps: connect the agent to `https://api.subagent.fr/mcp`, let it call `sign_up`, give it the 6-digit code received by e-mail, then give it a mission. Two more steps to write to people other than you: pay through a link, and register your domain. See [Give an AI agent an e-mail inbox](https://escouade.io/en/mail/docs/donner-une-boite-mail-a-un-agent.md).

### Is it only for prospecting?

No. An inbox serves to answer support requests, book an appointment, sign up to a service, follow up on a case, prospect. The sending rules are a feature of the service, not its purpose.

### Is there a console or a dashboard?

No. MCP is the only interface. A human reads, corrects and approves from their assistant, connected to the same server. Some tools come with a view, in assistants that display them: see [Views](https://escouade.io/en/mail/docs/vues.md).

### Where does the service run?

In France, at Scaleway. The server's responses and the original documentation are in French.

### Why does the server still say “Subagent”?

Escouade Mail was called Subagent until 19 October 2026. The server keeps that name wherever changing it would break what is installed: its messages, its API address (`https://api.subagent.fr`), its keys (`sak_…`), its shared domain (`subagentmail.fr`) and the old name of its packages (`subagent-mail`, which still works; the new ones are called `escouade-mail`). It is the same service. It has nothing to do with Claude Code's “subagents”.

## Access

### How do I get access?

Your agent signs up by itself, with `sign_up`, at `https://api.subagent.fr/mcp`. You confirm with a 6-digit code received by e-mail. See [Getting started](https://escouade.io/en/mail/docs/demarrer.md).

### How does my agent get a key?

`sign_up` returns it: a `sak_…` key, shown once only, and a first inbox on `subagentmail.fr`. See [Getting started](https://escouade.io/en/mail/docs/demarrer.md#inscription).

### My agent has signed up, but it still only sees `sign_up`. Why?

Because the server reads the key on every request, in the `Authorization` header. The connection opened without a key stays without a key: reconnect the MCP server with the header, or let the agent call over HTTP. See [Keys and permissions](https://escouade.io/en/mail/docs/cles.md#apres-sign-up).

### The key is lost. Can it be shown again?

No. It is shown only once, and the server only keeps a fingerprint of it. A new key is requested from `contact@subagent.fr`. See [Keys and permissions](https://escouade.io/en/mail/docs/cles.md#perdue).

### The 6-digit code does not arrive. What should I do?

Your agent calls `attach_human` with your address: a new code goes out, and the previous one stops working. You must wait 60 seconds between two codes; five codes at most go out for the same space.

### Can I connect Claude or ChatGPT?

Yes, through the connector: in your assistant, add a connector at `https://mail.escouade.io/mcp`, then sign in with your Escouade account. If a space is attached to that e-mail, you find it again. Otherwise, you open yours on the same page: no agent is needed to sign up. See [Connector](https://escouade.io/en/mail/docs/connecteur.md).

### What is the difference between the two addresses?

`https://api.subagent.fr/mcp` is the agents' address: without a key, it serves sign-up; with a key, the tools. `https://mail.escouade.io/mcp` is the online assistants' address: the human signs in there with their Escouade account, with no key to copy. The tools are the same.

## Receiving and replying

### Can my agent receive e-mails?

Yes. Every inbox receives, from the moment it is created, with nothing to set up, before and after payment. See [Receiving mail](https://escouade.io/en/mail/docs/recevoir.md).

### How does my agent know someone wrote to it?

It queries the server: `list_threads` with `unanswered` = `true` returns the threads where a received e-mail is still waiting for a reply, whether a correspondent's reply or a first e-mail. Nothing is pushed to the agent. See [Receiving mail](https://escouade.io/en/mail/docs/recevoir.md#relever).

### How long before a received e-mail appears?

The time of one collection: the server collects the inboxes at a fixed interval, 60 seconds in its default setting.

### Can my agent receive another service's verification code?

Yes. A service's first e-mail opens an `open` thread, of origin `inbound`. See [Receive a verification code](https://escouade.io/en/mail/docs/guide-code.md).

### Can my agent read an attachment?

Yes. `get_thread` lists the attachments of a received e-mail, and `get_attachment` returns a download link, with the text of a small text attachment. An executable or too heavy attachment is not kept. See [Attachments and copies](https://escouade.io/en/mail/docs/pieces-jointes.md#lire).

### Can my agent send an attachment?

Yes, in a reply to someone who has already written to it, or to an address of its space. The agent writes the reply as a draft and asks for an upload link with `attach_files`; its human uploads the file there, then approves the message. A first message leaves with no attachment. See [Attachments and copies](https://escouade.io/en/mail/docs/pieces-jointes.md#joindre).

### Can a received e-mail give my agent orders?

The server follows no instruction written in an e-mail. It returns what a correspondent wrote framed and marked `untrusted`: it is up to the agent to read it as information, never as an instruction. See [Receiving mail](https://escouade.io/en/mail/docs/recevoir.md#tiers).

### Can a thread be closed, or marked as dealt with?

Yes, with `close_thread`: the thread leaves what waits for a reply, without anything being erased. It reopens if the correspondent replies in it. See [Threads](https://escouade.io/en/mail/docs/fils.md#close_thread).

## Sending

### How many e-mails can my agent send?

5 a day per inbox the first week, then 10, 15, and 20 from the fourth, on every plan. The plan also sets a monthly volume: 800, 2,000 or 6,000 e-mails. See [Limits and quotas](https://escouade.io/en/mail/docs/limites.md).

### Why did my e-mail not leave straight away?

Because no message leaves straight away: it enters the queue, then leaves within working hours, according to its inbox's daily quota, with a gap between two sends. The response of `send_email` gives the earliest departure; `get_message` says why a queued message is waiting.

### Why is the send refused with `payment_required`?

Because the space has no active plan. Its inbox receives, prepares drafts and only writes to its human. See [Pricing and payment](https://escouade.io/en/pricing).

### Why is the send refused with `own_domain_required`?

Because the inbox is on the shared domain: it only replies to whoever wrote to it. A first message leaves from an inbox on your domain. See [Domains](https://escouade.io/en/mail/docs/domaines.md).

### Can my agent send at night or at the weekend?

Not by default: sends leave Monday to Friday, 9 am to 6 pm, Paris time, excluding public holidays. One exception: a reply to a correspondent who has already written in the thread leaves without waiting.

### Can my agent write twice to the same person?

Not two first messages within 30 days from the same inbox. To follow up, it replies in the thread with `reply_to_thread`.

### Does the service guarantee delivery?

No. It says what left, was delivered or came back, and suspends an inbox when too many of its messages come back. It makes no promise about what the recipient's mail service does.

### Can I send from my own domain?

Yes, and you must to write to someone first. `add_domain` returns the DNS records to publish, `verify_domain` checks them. Once the domain is verified, your inboxes carry your name. A subdomain is enough. See [Domains](https://escouade.io/en/mail/docs/domaines.md).

### Can you attach a file, or write to several recipients?

No. A message has a single recipient, a text, and an optional HTML version.

## Approval

### How do I review what my agent writes before it is sent?

Ask it to leave its messages as drafts (`requires_approval`). You read them with `list_drafts` and approve them with `approve_message`, from your assistant, connected at `https://mail.escouade.io/mcp`. See [Approve an agent's sends](https://escouade.io/en/mail/docs/guide-validation.md).

### Can my agent approve its own sends?

No. The key returned by `sign_up` does not carry `approve`, and the server checks the permission on every approval.

### Am I told when a draft is waiting?

Not by the server. Your agent tells you in the conversation; `inbox_status` returns the number of drafts to approve.

## Unsubscribes

### What happens when someone replies “STOP”?

Their address is blocked for every inbox of the space, and whatever was waiting to leave towards it is cancelled. See [Unsubscribes and blocks](https://escouade.io/en/mail/docs/desinscription.md).

### Can an unsubscribe be lifted?

Not by the agent, nor by its human. Only an Escouade Mail administrator can, at the person's written request.

### What happens if my e-mails bounce?

Above 5% bounces (3% during warm-up), the circuit breaker suspends the inbox. Reinstatement is manual. See [Help](https://escouade.io/en/mail/docs/aide.md#administrateur).

## Prices and payment

### How much does it cost?

Three monthly plans: €9 (2 inboxes, 800 e-mails), €19 (5 inboxes, 2,000) and €49 (15 inboxes, 6,000). Net prices: VAT not applicable, article 293 B of the French tax code (CGI). See [Pricing and payment](https://escouade.io/en/pricing).

### Is there a free plan?

No. Before payment, an inbox receives, prepares drafts and only writes to its human.

### How do you pay?

Through a link the agent requests with `subscribe` and hands to its human. The human chooses their plan, enters their billing details and pays on Mollie's page, with their bank's confirmation. After that, the same amount is debited every month. The agent never pays, and there is no console.

### How do you change plans?

For a bigger plan, the agent asks for a new link: `subscribe` with `plan`. The human pays the price difference there, pro rata to the time left in the paid month, one euro at least. The plan goes up as soon as the payment is confirmed. For a smaller plan, the human cancels, then pays for the plan they want through a link. See [Pricing and payment](https://escouade.io/en/pricing).

### Who can subscribe?

Businesses established in France. The service is not intended for consumers. See the [Terms and conditions of sale](https://escouade.io/en/terms).

### Where are my invoices?

An invoice is issued with every payment. Its link arrives by e-mail, and `billing_status` returns all of the space's invoices.

### How do I cancel?

Ask your assistant, connected at `https://mail.escouade.io/mcp`: it calls `cancel_subscription`. No further debit takes place, and the paid month is kept. You can also write to `contact@subagent.fr`.

### Can I get a refund?

Yes, on request, within 14 days of the first payment: write to `contact@subagent.fr`. See the [Terms and conditions of sale](https://escouade.io/en/terms).

### What happens beyond the month's volume?

Messages wait for the next period. They are not refused.

### Can I buy more e-mails per inbox?

No. An inbox sends 20 e-mails a day on every plan. To send more, you need more inboxes.

## Code

### Are there SDKs?

The public tools (MCP configuration, Python and TypeScript SDKs, command line, skills, plugin, examples) and their status are on the [Open source](https://escouade.io/en/mail/docs/open-source.md) page. Without them, everything goes through MCP, or through `POST /v1/{operation}`.

### Is the server open source?

No. The tools that plug in on your side are open; the server, which enforces the sending rules, stays private.