agentmail

Create and manage agent-owned email inboxes via the AgentMail CLI.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill agentmail-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentmail
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/email/agentmail
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill agentmail-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agentmail-cli, and includes references (resource) components.

What problem does it solve? Agents often need their own email inbox to send messages, receive replies, complete email OTP verification flows, and react to inbound mail, but configuring IMAP/SMTP access to a human mailbox is fragile and inappropriate. This Skill gives an agent a dedicated AgentMail inbox controlled entirely through a CLI. ## Core Features & Use Cases - Agent-Owned Inboxes: Create inboxes, send and receive mail, reply in threads, forward messages, apply labels, and fetch attachments using the agentmail CLI. - Self-Signup and OTP Flows: Register a new AgentMail account without an existing API key and complete OTP verification with a human's help. - Realtime Inbound Delivery: Receive message.received events through webhooks (Svix-signed) or WebSockets for local agent processes. - Use Case: An agent handling customer support creates a [email protected] inbox, polls for unread messages, replies in threads, and labels messages as handled once resolved. ## Quick Start Install the agentmail CLI with npm, export your AGENTMAIL_API_KEY, and ask the agent to list inboxes and send a test email from its own AgentMail inbox.

Frequently Asked Questions about agentmail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent its own email inbox?▼

Install the agentmail CLI with npm, export an AGENTMAIL_API_KEY, and run agentmail inboxes create with a username and display name. The agent can then send, read, reply, and label mail from that inbox using CLI commands.

How to sign up for AgentMail without an API key?▼

Run agentmail agent sign-up with a human email and username, then export the returned api_key and verify with agentmail agent verify using the OTP sent to the human. Before verification the account has one inbox and a 10 sends per day limit.

Should I use the AgentMail CLI, MCP, or REST API?▼

Use the agentmail CLI as the default path for all inbox and message workflows. Use the hosted MCP server only when the harness expects MCP tools, and fall back to the REST API only when the CLI lacks a required operation.

How do I receive inbound email in realtime with AgentMail?▼

Use webhooks when a public HTTPS server can receive Svix-signed events, or WebSockets for a local agent process without a public URL. Subscribe to message.received events, dedupe by event_id, and handle replies through the CLI.

Why does my AgentMail agent loop on its own sent messages?▼

Loops happen when the agent reacts to message.sent or delivery events instead of only message.received. Filter inbound events strictly, dedupe by svix-id or event_id, and never treat the agent's own outgoing mail as new work.