---
title: "AgentMail inboxes now add a signature: what changes for your agents"
url: https://signatoro.com/blog/agentmail-inbox-signature
description: "Since October 28, 2026, an AgentMail inbox can carry a signature that AgentMail adds to every message it sends. How the setting works, its limits, how it meets a signature your agent already appends, and how to fill it from your saved Signatoro signature."
published: 2026-11-19
updated: 2026-11-19
---

# AgentMail inboxes now add a signature: what changes for your agents

Since October 28, 2026, an AgentMail inbox can carry a signature that AgentMail adds to every message it sends. How the setting works, its limits, how it meets a signature your agent already appends, and how to fill it from your saved Signatoro signature.

Since October 28, 2026, an AgentMail inbox can have a signature of its own. Set it once on the inbox and AgentMail adds it to every message the inbox sends, through the API, the MCP server or SMTP. An agent that already appends its signature before each send keeps working: AgentMail does not add a signature to a message that already contains it. What changes is where you keep the signature, and that two copies can now drift apart.

## What AgentMail shipped

AgentMail's changelog entry for October 28, 2026 opens: "Inboxes can now carry a signature that AgentMail adds to every message they send." The inbox docs and the API reference fill in the rules:

- **One setting per inbox.** `signature` is an object with `text` and an optional `html`, set when the inbox is created or later with an update. Sending `signature: null` removes it. The inbox's responses include it when one is set.
- **Every send path.** It goes on sends, replies, reply-alls, forwards and drafts, "including scheduled ones", whether they come from the API, the MCP server or SMTP.
- **Placement.** "Right after your content, above any quoted or forwarded message."
- **No duplicates.** "If your message body already contains the signature, it is not added again."
- **Text and HTML.** `text` goes in the plain-text part. Without `html`, the HTML part gets `text` with its line breaks.
- **Size.** `text` is at most 1,000 characters and `html` at most 4,000, "so link images by URL rather than embedding them."
- **One exception.** Visa TAP messages are sent exactly as written, without the signature.

Before this, AgentMail's send endpoint took a plain-text and an HTML body and had no signature parameter, so the agent had to build the signature into the body itself. Our [agent mailbox post](https://signatoro.com/blog/agent-mailbox-email-signature) described that older behavior, as checked on October 14, 2026.

## What it means for an agent that already signs

Until October 28, an agent on AgentMail that signed its email had to append the signature to both bodies itself, often fetched right before the send. Three cases follow from AgentMail's rules:

1. **No inbox signature set.** Nothing changes. The setting is opt-in, and the inbox sends what the agent built.
2. **Inbox signature set, and it matches what the agent appends.** AgentMail sees the signature already in the body and does not add it again. You get one signature.
3. **Inbox signature set, and it differs.** The rule is about "the signature", the one stored on the inbox. If the agent appends a newer version and the inbox still holds last month's, the body does not contain the stored one, so AgentMail adds it. The email goes out with two signatures, one of them out of date.

Case 3 is the one to watch. It happens when someone changes a title or a phone number in one place and not the other. A team that already fetches at send time can leave the inbox setting empty. A team that wants the inbox to sign by itself can turn off the agent's own signature step and keep the inbox copy current.

## Choose where the signature lives

| Approach | What signs | Keeping it current |
| --- | --- | --- |
| The agent fetches and appends it before each send | The agent, with the signature fetched for that email | Each send reads the saved version |
| AgentMail's inbox signature | AgentMail, on every send path, even when the agent forgets | A copy on the inbox, updated whenever the signature changes |
| Both | AgentMail skips its copy only when the body contains it | Two copies that must match exactly |

The inbox setting is the safer net for an agent that sometimes skips a step. Fetching at send time keeps one source of truth and works on any mailbox the agent moves to.

## Fill the inbox signature from Signatoro

If you keep your agents' signatures on Signatoro, the agentic email signature platform, you can copy one into the AgentMail inbox the agent sends from. Add the agent on Signatoro first, as a company AI agent or one of your AI assistants, with its own API key.

1. **Fetch the agent's signature** with its own key:

   ```
   GET https://signatoro.com/api/v1/signature
   Authorization: Bearer <the agent's Signatoro key>
   ```

   A key bound to an agent always returns that agent's signature, as `html` and `text`.
2. **Check the length.** AgentMail allows up to 4,000 characters of `html` and 1,000 of `text`. A designed signature built from tables and inline styles can be long, so check yours before you store it. Pictures already sit at a public web address, the form AgentMail asks for.
3. **Store it on the inbox** with an update, in code that passes the two values straight through:

   ```
   PATCH https://api.agentmail.to/v0/inboxes/<inbox address>
   Authorization: Bearer <your AgentMail key>
   Content-Type: application/json

   {"signature": {"text": "<text from step 1>", "html": "<html from step 1>"}}
   ```

   Pass them from the response in code, never retyped by a model: Signatoro's replies say so too.
4. **Run it again after every change** to the agent's signature: a new title, a new logo, a new AI line. Signatoro's [webhooks](https://signatoro.com/docs/install-signature/agent/webhooks) post an event when a person's signature changes, but they do not cover AI assistants' or company agents' signatures yet, so trigger the update yourself, for example from the job that changes it, or on a schedule.
5. **Send one test email** from the inbox and read it as the recipient sees it: one signature, the right phone and email address.

If the signature is too long for the inbox setting, or you would rather not keep a second copy, keep fetching at send time and leave the inbox setting empty. The [AgentMail page](https://signatoro.com/email-signatures-for-ai-agents/agentmail) and the [email API guide](https://signatoro.com/docs/install-signature/agent/email-apis) show that route.

**One signature for every agent inbox**

Give each agent its own name, role and AI line on Signatoro, and fetch it with the agent's own key, at send time or into the inbox setting.

[Set up an AI agent](https://signatoro.com/docs/install-signature/agent) | [See pricing](https://signatoro.com/pricing)

## Frequently asked questions

### Does AgentMail support email signatures now?

Yes, since October 28, 2026. An inbox can carry a `signature` with `text` and an optional `html`, and AgentMail adds it to sends, replies, reply-alls, forwards and drafts from the API, the MCP server and SMTP.

### Will my agent's emails get two signatures?

Not if the inbox setting is empty, and not if the agent appends exactly the signature stored on the inbox. They can if the two differ: AgentMail skips its copy only when the body already contains it.

### Can each agent have its own signature?

The setting is per inbox, so each agent with its own inbox can carry its own. Several agents sending from one inbox share that inbox's signature, unless each appends its own and the inbox setting stays empty.

### Can an AgentMail signature include a logo?

Yes, as a picture linked by URL in `html`. AgentMail's docs say to link images rather than embed them, because `html` is limited to 4,000 characters.

### Does the inbox signature change when I edit my signature on Signatoro?

No. The inbox holds a copy. Update it after each change, or skip the copy and let the agent fetch the signature before each send.

## Sources

Read on November 9, 2026:

- [Changelog, October 28, 2026 entry (AgentMail docs)](https://docs.agentmail.to/changelog)
- [Inboxes: Signatures (AgentMail docs)](https://docs.agentmail.to/inboxes#signatures)
- [Update Inbox, InboxSignature (AgentMail API reference)](https://docs.agentmail.to/api-reference/inboxes/update)
- [What can I do with an AgentMail inbox? (AgentMail knowledge base)](https://docs.agentmail.to/knowledge-base/inbox-capabilities)
