# The email runtime for agent fleets.

When your product’s agents email real people. One API for your domains and customers’ Gmail or Outlook, with threading, PDF parsing, and sending guardrails built in.

[Get started](/signup) [Read the docs](https://docs.aiinbx.com)

Email runtime

## Sending is easy. Real-world email breaks agents.

Everything handled between raw email and your agents.

### [Attachments & signals](/features/attachments)

Example: a scanned Quote.pdf is read by OCR into a Markdown table (3mm, 500, €4.20). An out-of-office arrives with back_on: Nov 27, and a sign-in mail with code: 482 913, both as typed fields.

Scanned PDFs become Markdown. Out-of-office dates and codes arrive typed.

### [Classified on arrival](/solutions/auto-reply-detection)

Example: five emails arrive and every one is delivered, each labelled with its category: human, out_of_office, bounce, verification and marketing. Your code reads the category and decides what to wake, pause or skip.

Every email arrives with a category, so your code decides what to wake, pause, or skip.

### [Runaway-agent caps](/features/pacing)

Example: a rule of 3 per hour per recipient. Your agent misfires 8 replies to marco@lindmetall.de in one hour: 3 are delivered and the other 5 are held for later.

Cap sends per recipient, per sender, or across the workspace so a looping agent never burns your domain.

### [Broken threads](/features/threading)

Example: three replies arrive from a new sender, with no reply headers, and under a renamed subject. All three land on one thread, thr_8f2c, next to the mail that started it.

New sender, dropped headers, or renamed subject still land on one thread.

### [Sending hours](/features/sending-hours)

Example: a sending-hours rule opens weekdays 09:00–18:00 and Saturday 10:00–13:00. 'Following up on RFQ 4471' sent Sunday 02:47 is held and released Monday 09:00.

Define when sending is allowed, by timezone. Mail queued outside those windows waits for the next open slot.

### [Auto opt-outs](/features/suppressions)

Example: Iris Kaplan replies “Not for us, please take me off your list.” She is added to your suppressions, and the next campaign, on the new 4mm range, is blocked for her.

Unsubscribe links, one-click headers, and plain-text replies asking to stop are added to your suppression lists automatically, per campaign or workspace.

How it works

## Send with one call, hear back on one webhook

The send call applies your guardrails. When a person replies, the webhook brings their email already threaded and cleaned, with the attachments ready to read.

[Follow the quickstart](https://docs.aiinbx.com/quickstart) [API reference](https://docs.aiinbx.com/api)

send.ts

```
const email = await aiinbx.emails.send({
  from: "nora@yourapp.com",
  to: "dana@lindmetall.de",
  subject: "RFQ 4471: 3mm brushed sheets",
  text: draft,
  suppression_key: "q4-outbound",
})
 
// Sunday, 02:47. A pacing rule holds it until Monday morning.
email.status                    // "queued"
email.pacing.estimated_send_at  // "2026-08-31T07:00:00Z"
email.pacing.held_by            // { kind: "hours", rule_id: "pace_…" }
```

Sent on a Sunday night. The response says which rule held it, and until when.

- [SDKs](https://docs.aiinbx.com/sdks): Typed clients for TypeScript and Python, with webhook verification built in. npm install aiinbx
- [CLI](/features/cli): Every API call from a terminal or a script, as one binary. npm install -g @aiinbx/cli
- [MCP server](/features/mcp): Claude, ChatGPT and Cursor set up and run your workspace through the same API. https://mcp.aiinbx.com/mcp
- [Agent skills](https://docs.aiinbx.com/skills): Your coding agent wires sending and receiving into your app and tests it. npx skills add aiinbx/skills

Two ways to connect

## Any domain, or any Gmail and Outlook mailbox

Run on our mail infrastructure, connect Gmail or Outlook, or both. Every email flows through the same runtime.

Example: mail on your domain, mail.yourapp.com, runs on AI Inbx mail infrastructure; Gmail and Outlook mailboxes connect over OAuth. Both flow into the same AI Inbx runtime (threads, replies, OCR, guardrails) and out through one API and webhook: email.received in, threads.reply out.

### One runtime for both

Domain mail and connected mailboxes get the same threading, reply parsing, OCR, and guardrails, then reach you through one API and webhook.

### [Domains on our mail servers](https://docs.aiinbx.com/guides/domains)

Example: mail.yourapp.com is verified. Its DNS records (DKIM as TXT, SPF as TXT, DMARC as TXT, Return path as MX, Inbound as MX) are all found; the inbound MX record is only needed for receiving.

Publish DNS once, for your own domain or a customer's, and every address on it sends and receives on our mail servers.

### [Gmail & Outlook mailboxes](/features/mailboxes)

Example: tom@harbourly.com at Harbourly and jana@rheinbau.de at Rheinbau are connected through Yourapp, your own OAuth app, each in its customer’s space.

Connect any Gmail or Outlook mailbox over OAuth, your team's or your customers', with the same threads and webhooks and no IMAP to run.

### [Multi-tenant spaces](/features/spaces)

Keep every customer's domains, mailboxes, pacing rules, and sending reputation isolated under one API key.

Console

## See what your product sent and what came back

Inspect threads, queues, spaces, and suppressions in the console, or drive everything via API, CLI, and MCP.

The console's thread page shows all four messages of the thread in order, each labelled with its category (out of office, human). Under each smart-matched message it says why it belongs to this thread, such as Marco covering for Dana and Dana confirming the price.

Production fundamentals

## Everything else production email needs

EU or US mail regions, replayable webhooks, human-in-the-loop drafts, and live DNS diagnostics, all built in.

- **Domains**: Add a domain and we tell you exactly which DNS record is wrong.
- **Regions**: Choose EU (Frankfurt) or US (N. Virginia) mail servers per domain for sending, receiving, and attachment storage. Core database and processing run in the EU.
- **Webhooks**: Signed, retried for 24 hours, and replayable for when your server was down.
- **Reply parsing**: Quoted chains and repeated signatures removed cleanly, with inline answers kept in context.
- **Scheduled send**: Pass a timestamp and it sends then, unless a pacing rule holds it. Move or cancel it until it goes.
- **Drafts**: Let your agents save drafts for a person to review, edit, and send, in the console or in your own UI.
- **Sender checks**: Mail to your domains carries its SPF, DKIM, DMARC and spam verdicts.
- **Metrics**: Spot bounces and complaints before a provider throttles you.
- **Tracking**: Optional open and link-click tracking, in the metrics and on your webhook.

Use cases

## One runtime for software that runs real conversations

Autonomous email agents, reputation-safe outreach, and multi-tenant SaaS.

- [AI email agent](/use-cases/ai-email-agent): Software that holds the conversation end to end.
- [Cold outreach](/use-cases/cold-outreach): Sequences at a pace a domain survives.
- [Multi-tenant SaaS](/use-cases/multi-tenant-saas): An inbox and a domain for every customer.

Pricing

## Priced by how much email you send and receive

From $5 a month with 5,000 emails. Every feature is included on every plan. Only email volume, domains, mailboxes, and pacing rules scale.

[See pricing](/pricing)

- Developer$5a month, 5,000 emails
- Growth$29a month, 30,000 emails
- Scale$99a month, 100,000 emails

## Let AI Inbx handle the email. Spend the week on your agents instead.

[Get started](/signup)
