# Carry a conversation with outside people over days

> Carry a conversation with outside people over days: 1 companies fully do it, 10 with a limit, 51 carry the tag. Every listing in Agent inbox APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-inboxes.multi-day-thread/
- Markdown: https://www.anchorterminal.com/niches/agent-inboxes.multi-day-thread/index.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-inboxes.multi-day-thread/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-inboxes.multi-day-thread/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 10 | 51 | 15 | 5 |

## What counts as done

A reply arriving days later is matched to the original thread, visible to every list and search call, and the agent's answer shows in the same conversation in Gmail and Outlook.

How agents ask for it: follow up with the vendor if they don't reply; keep negotiating this by email; reply to the client in the same thread; pick up where the thread left off

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **InboxAPI (Sitka Capital Pty Ltd)**: send_reply sets In-Reply-To and References, get_thread rebuilds a conversation from any Message-ID, and mail failing SPF or DKIM is still returned, labelled suspicious rather than hidden.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AgentMail API + MCP (AgentMail, Inc.)**: Threads group replies and reply endpoints keep the conversation, with extracted_text removing quoted history. Open issue 38 (a16) shows replies from domains without SPF or DKIM hidden from MCP list and search until relabelled.
- **Cherami (Abderrahmane Gourragui (sole operator, Quebec))**: Conversations have list and read endpoints, sends take in_reply_to, and content.reply_text holds the new reply without quoted history. Whether mail from senders without SPF or DKIM is still listed isn't documented.
- **Clawpost (Frank Harris)**: list_threads, get_thread and reply_to_message (which preserves threading) carry a conversation, and full-text search covers bodies, but get_thread returns only approved messages and no quoted-text stripping is documented.
- **Hostinger Agentic Mail (Hostinger International Limited)**: Folders, IMAP-style search and a send with inReplyTo let an agent answer in-thread from a real mailbox, but there is no threads endpoint or quoted-text stripping, so matching replies is left to the agent.
- **Inbound (EXON ENTERPRISE LLC)**: GET /api/e2/mail/threads/{id} returns the whole conversation and POST /emails/{id}/reply answers in it, but whether cleanedContent strips quoted history isn't stated, nor whether unauthenticated senders are listed.
- **Lumbox (Cyphen Innovations Private Limited)**: Threads and replies are documented and stripped_text removes quoted replies and signatures, but whether a reply from a domain without SPF or DKIM stays listed isn't stated.
- **mails.ai Agent Email (Mails.ai)**: Threads are rebuilt from In-Reply-To and References so replies land on the same thread_id, with search, folders and notes. Whether mail without SPF or DKIM stays visible to list and search wasn't found in the docs read.
- **MailSlurp (Pettman OÜ)**: get_email_thread and reply_to_email keep thread context, but outside correspondents can only be reached on Pro and above, and the docs read don't say how unauthenticated senders are listed.
- **Postfleet (Postfleet)**: Messages carry thread_id, listing filters by thread_id, since, until and q with a cursor, and reply_email answers in-thread, but whether unauthenticated senders are listed isn't stated, and sends have no cc or bcc.
- **Robotomail (Tiny Bot Labs Limited)**: Messages carry threadId with a thread filter, and sends take inReplyTo, which must be the RFC Message-ID, not the Robotomail id. Quoted-text stripping and handling of unauthenticated senders aren't documented.

- not this job: Mailows (DW Technology LLC): The API manual has no thread or reply endpoint and no In-Reply-To field on send, so a days-later reply can't be matched or answered in the same conversation by the service.

## What stops agents finishing

- reply from a domain without SPF or DKIM hidden from list and search
- no thread or reply endpoint (Mailows)
- retention shorter than the conversation

## Around it

Before: agent-inboxes.own-identity, personal-assistants.errand-outreach. After: scheduling.book-meeting, crm.log-activity.

## Where this comes from

Weight 15 of 100 in Agent inbox APIs: 5 of 31 accounts: threads that were too hard to build alone (a01), client mail (a08), per-agent reply tools (a09), agents coordinating by email (a12) and a client reply hidden from the MCP (a16)

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-inboxes.multi-day-thread.json, or the MCP tool get_use_case with id agent-inboxes.multi-day-thread. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
