Everything your agent’s inbox does.

A real address on agents.agentboxd.com the moment you ask. Pass a client_id and a restarted agent gets its own inbox back instead of a new one.

Connect a subdomain such as mail.yourcompany.com. We show the MX, SPF, DKIM and DMARC records, check them, and sign mail with the domain’s own DKIM key.

Receive-only addresses on their own domain, tmp.agentboxd.com, that wipe themselves and every message in them after 1 minute to 24 hours. They don’t count toward your inboxes.

Every inbound message is checked. Failures get the spf-fail or dmarc-fail label and a warning in MCP results.

Quoted history and signatures are cut away, so your agent reads the new sentence instead of the whole chain. Replies are threaded by Message-ID and References, never by subject.

One call waits for the sign-up email and returns the code or link with a confidence score. No inbox scraping, no regex on your side.

JEV sorts each message into a category (support, sales, billing, verification…) and scores prompt injection, phishing, needs-a-human, auto-reply and urgency. Scores are stored, labels such as ai:injection-risk are added.

Files are stored with their size, type and SHA-256 and served back with safe headers. The original message is always available.

Ranked full-text search over subject, body and sender, and a wait call that returns the moment the next matching email lands.

A record per sender with notes your agent keeps, documents it can search, and your own ids (crm_id, order numbers) on contacts, inboxes and threads.

Mail goes out from the agent’s own address through our own delivery servers. Replies set In-Reply-To and References and stay in the thread.

The agent writes a draft; a person edits and approves it in the dashboard’s Drafts tab, or a supervising agent sends it. Give the agent drafts:write without messages:send and it can’t send at all.

Schedule a draft or a send from 1 minute to 30 days ahead. Every check runs again at send time; cancel or reschedule until then.

A suggested answer built from the thread, the contact and your knowledge documents, with the documents it used. Never sent on its own; save it as a draft for review.

Addresses and domains to accept or refuse, for receiving, sending and replying, per inbox or for the whole workspace. Blocked mail is kept and hidden, never lost.

A 5-minute burst limit, a daily cap per workspace and per inbox, and a rate limit per key. Hard bounces and complaints add the address to a suppression list.

MCP results that carry email start with a data-not-instructions line, and flagged mail gets a warning field before the model reads it.

A zero-dependency TypeScript client and a Python client (sync and async) named agentboxd, reading AGENTBOXD_API_KEY from the environment.

Tools for Claude Desktop, Claude Code, Cursor or any MCP client: inboxes, mail, codes, contacts, knowledge, drafts and sign-in. No code.

A POST for every event, signed with HMAC-SHA256 and retried for about a day. The event catalog shows every body; envelope payloads send ids and subjects only, no content.

The same events over a WebSocket your agent opens. No public URL, so it works from a laptop or behind NAT, and the SDKs reconnect and resume on their own.

Send from any SMTP client or library on port 587 or 465, with an API key as the password. Same checks, signing and events as an API send.

Scope a key to one inbox and give it only the permissions its job needs, from presets such as read-only, send and read, or sign-in only.

Inboxes, threads, drafts, contacts, knowledge, webhooks and keys in one place, with sent, delivered, bounced and received mail per hour or day, and a “Use the API” button with each page’s calls pre-filled.

Your agent asks for a 5-minute, single-use ID token addressed to one app and signs in with it. No password to store, no email loop.

Apps register a client in the dashboard and verify tokens with any OIDC library: discovery, JWKS, code flow with PKCE and a consent screen, or a server-side token exchange.

Each app sees a different, stable subject for the same agent, so apps can’t link your agents across services. Every sign-in is logged and fires a webhook.

An agent with no API key gets its own workspace and inbox with one call and a short proof of work. It can receive and reply at once; a person claims it later to lift the sending limits.

The API, mail servers, database and stored mail run in France, with a second EU server for backups.

One workspace setting decides whether any email content goes to a model. Off keeps everything on our servers; login codes still work.

Nightly backups, encrypted before they leave the server, restore-tested every quarter, and health checks every 5 minutes.

Mail is kept for your plan’s retention and deleted daily after that. Choose a shorter period in Settings; a message labelled keep never expires.

A Data Processing Addendum, and a list of every third party that handles customer data, what it receives and where.

A dedicated deployment in your cloud account or region, on S3-compatible storage, with your domains and sending IPs and the same API.