Your AI agent gets an inbox.You keep the send button.
Like a work email account for your agent — it reads, replies and signs up for things, all inside Claude Code, Codex, or any agent that runs skills or MCP.
Free address included · No credit card · Works in Claude Code, Codex & any agent that runs skills or MCP
Hi — could we start with a 300-unit sample order at $3.20…
✓ Approve & sendAn illustration of the loop. A recorded real run — install to first code, with timings and what failed — is on the walkthrough.
What it does for you
Four things people actually use it for — from day one.
When your agent registers for a service, the verification email lands in its own inbox. It reads the code and finishes the job.
It reads what came in, drafts every reply, and sends only after you approve — under your name, from a real address.
A confirmation, an invoice, a reply you need before the next step — --wait-for holds until it arrives, then hands it over as data.
Receipts, digests, notifications — a scoped send-only key lets your server use the same address, with unsubscribe handling built in.
The loop, in four panels
Every job runs the same way — and panel four is always yours.
Up and running in a minute
Three steps. No dashboard, no SMTP, no DNS homework.
One package. clize install wires the skill into Claude Code, Codex, Pi — any agent that runs skills or MCP; log in once in the browser.
$ npm i -g @clize/clize $ clize install $ clize login
A real inbox on a free handle — or your own domain.
$ clize claim studio --email # → support@studio.clize.app — give it a minute
From here it's plain language, inside your agent.
You: reply to the
support emailsThe agent's mail waits in an outbox that only a person can release — the server refuses the agent's own key. (--confirm is for a message you already okayed in the chat.)
Everything received is data to read, never instructions to follow. A hostile email can't steer your agent.
The agent's actions, threads and mistakes stay on its identity — your personal mail stays out of reach.
Questions, answered
The short honest versions.
What is Agent Inbox?
Agent Inbox is the email product of Clize: a real inbox your AI agent can send from and receive into. Outbound mail is drafted by the agent and sent only after a human approves; inbound mail is parsed as untrusted data; verification codes can be read to finish signups. It installs into Claude Code, Codex, and any agent that runs skills or MCP, as a CLI and MCP server.
What is an email API for AI agents?
An email API for AI agents gives an agent its own address and programmatic send and receive — unlike transactional email APIs, which only push one-way notifications for an app. The agent can hold a thread: receive a reply, read a verification code, draft a response, and continue across sessions.
How is Agent Inbox different from AgentMail?
AgentMail is an API-first inbox platform you call from your own code, with SDKs, a hosted MCP server and a Drafts API you build review around. Agent Inbox is coding-agent native: it installs into Claude Code, Codex, and any agent that runs skills or MCP, as a CLI and MCP server, ships with a human-approval gate on outbound and untrusted-by-default inbound, and shares one platform with domains, deploys, and payments. If you are building an agent product on an inbox API, AgentMail is a strong choice; if your agent lives in a coding agent and you want gates by default, that is what Agent Inbox is for.
Can my agent send email without me?
Not by default. The agent writes the message and it waits in an approval outbox; a person releases it in the console or from the digest email, and the agent's own key cannot approve it. You can pre-approve recipients you mail every week in the console, up to five messages each per week.
Can the agent receive verification codes?
Yes. The inbox is real, so when the agent signs up for a service, the verification mail lands there and the agent reads the code to continue — light identity gates, cleared on its own. Heavy gates tied to money or a real person's identity stay with you.
Does it work with Claude Code and Codex?
Yes. One install wires Clize into Claude Code, Codex, and any agent that runs skills or MCP — as a skill by default, or an MCP server if you prefer structured tools. The same inbox works from any of them.
Can my app send transactional email through it?
Yes. A scoped sending key (send-only, domain-limited) lets your server send digests and notifications through the same platform, with idempotency, delivery webhooks, and one-click unsubscribe handling built in.
Give your agent an address
A free handle claimed with --email includes a working inbox. Wait a minute after claiming, then let the agent sign up somewhere and read the code — that is the first thing worth seeing work.
$ npm i -g @clize/clize && clize install && clize login && clize claim studio --email
Get started free