# Sending APIs vs an inbox for AI agents

> Sending APIs are built to send receipts and newsletters. An AI agent that must receive, thread and reply needs an inbox. How to tell which job you have.

Source: https://trotta.email/compare/sending-apis

Use a sending API when software sends and nothing comes back: receipts, alerts and newsletters, at volume. Use an inbox when an AI agent must receive mail, keep a thread and reply, because that takes a mailbox, screening of what arrives and checks on what leaves. A product can use both.

Updated November 20, 2026

A sending API, also called a transactional email API, turns an HTTP call or an SMTP login into delivered mail. It is the right tool for mail that goes one way. An agent holds conversations, and that is a different job.

## A sending API and Trotta Mail side by side

|  | Sending API | Trotta Mail |
| --- | --- | --- |
| Built for | Applications that send: receipts, password resets, newsletters. | AI agents and humans, in conversation. The guard is stricter for an agent. |
| When mail is screened | Incoming mail is not the product. If inbound parsing is offered, ask whether anything is screened before your webhook fires. | While the sending server is still connected, before the message is accepted. |
| What an agent can read | Usually a parsed message posted to your endpoint as it arrived. Ask whether there is a stored mailbox at all. | The safe view: hidden text removed, instructions aimed at a model marked, risky links defanged. |
| Held mail and human review | Rarely part of the product. Ask where a risky incoming message goes. | Held outside the inbox. A human can release it. An agent's key cannot. |
| Outgoing checks | Checks that protect sender reputation: bounces, complaints, suppression lists. Ask whether content is checked for secrets. | Screened for secrets, sensitive data and replies steered to a new address. |
| Sign-in codes | The API sends codes for your app. Receiving a code for an agent takes an inbox. | Parsed for the agent in its own inbox. Sealed from every API key in a human's mailbox. |
| Setup for many agents | Sending as any number of senders is simple. Receiving for each one is routing you build. | One API call per inbox. Pods keep each customer's inboxes apart. |
| Price to start | Usually by volume sent, often with a free tier. Check the provider's page. | Free: 2 inboxes, 1,000 emails a month. Developer, $20 a month: 5 inboxes, 5,000 emails. Startup, $200 a month: 50 inboxes, 50,000 emails. |

## When a sending API is the better choice

- Mail goes one way, at volume: receipts, alerts, newsletters.
- You need deliverability tooling for bulk mail, such as dedicated IPs, bounce handling and suppression lists.
- You need templates, and analytics on opens and clicks.
- Your software speaks SMTP and nothing else, and needs a relay.

If your agent sends notifications and no reply ever needs reading, use a sending API. Trotta Mail is not a bulk sender. Its plans cap sends at 50 a day on Free, 500 on Developer and 5,000 on Startup.

## What an agent needs that a sending API leaves to you

- **A place to receive.** A real address that accepts replies, with each message stored.
- **Threads.** Each reply tied to its conversation, so the agent sees what was said before.
- **Screening of what arrives.** Replies come from strangers. Text written to hijack a model should be caught before the agent reads it.
- **Checks on what leaves.** An agent can be tricked into sending a secret. Something should look before the message goes.
- **A [human in the loop](https://trotta.email/learn/human-in-the-loop-email).** Somewhere for uncertain mail to wait.

You can build these on inbound parsing and a database of your own. Ask how much of it you want to own, and who screens the parsed message before your agent reads it. To buy it built, see the [checklist for agent inbox APIs](https://trotta.email/compare/agent-inbox-apis).

## Using an SMTP API from an AI agent

An AI agent can use an SMTP API to send. An SMTP login and an HTTP send call both put mail on the wire. Neither gives the agent a mailbox, so replies need somewhere to land.

Trotta Mail itself has no SMTP or IMAP access for mail clients. An agent works through the REST API, the MCP server or the TypeScript and Python SDKs.

## What moving looks like

Keep the sending API for bulk and product mail. Add an inbox for conversations.

1. Create an inbox with one call. Use its address where replies should land.
2. Receive replies with a webhook, live events or the `wait` call. See [webhooks or polling](https://trotta.email/learn/email-webhooks-vs-polling).
3. Reply in the thread with `POST /v1/messages/{id}/reply`. Outgoing mail is screened before it leaves.
4. On a paid plan, put agent inboxes on a subdomain of your own domain.

## Questions

### What is the difference between a transactional email API and an inbox?

A transactional email API sends mail from your software. An inbox receives mail, stores it, threads it and lets its owner reply.

### Can an AI agent use an SMTP API?

To send, yes. To hold a conversation it also needs a mailbox that receives replies, and something to screen them before the agent reads.

### Can I use a sending API and an agent inbox together?

Yes. Send receipts and newsletters through the sending API, and give the agent its own inbox for mail it must read and answer.

### Does Trotta Mail replace my sending API?

Not for bulk mail. Sends are capped by plan, from 50 a day on Free to 5,000 a day on Startup. Trotta Mail is built for conversations.

## Sources

- [Trotta Mail API summary for agents](https://api.trotta.email/llms.txt)
- Trotta Mail docs: concepts, plans and limits, webhooks, live events

## Related

- [Email API for AI agents](https://trotta.email/learn/email-api-for-ai-agents) Guides
- [Email webhooks vs polling](https://trotta.email/learn/email-webhooks-vs-polling) Guides
- [Data exfiltration through agents](https://trotta.email/threats/data-exfiltration-through-agents) Threat library
- [Pricing](https://trotta.email/pricing)
- [Security](https://trotta.email/security)
- [Quickstart for agents](https://trotta.email/docs) Docs

Every check is on, on every plan. Free for two inboxes. No card.

[Get an inbox](https://trotta.email/signup) [See pricing](https://trotta.email/pricing)
