# Mailgent > Email and identity for AI agents. Give every agent a real inbox at name@mailgent.dev, plus a vault, 2FA, calendar, a did:web identity, and a USDC wallet — over a clean API or MCP. Mailgent is the identity stack for AI agents. It leads with email: a real, deliverable address every agent can send and receive from. Identity is the root of trust, and mail, vault, 2FA, calendar, and payments are the capabilities that hang off it. One signup call provisions all of it. ## Capabilities - [Mail](https://mailgent.dev/mail): A real inbox at name@mailgent.dev over API or MCP. - [Vault](https://mailgent.dev/vault): Encrypted, scope-gated credential store. - [2FA / TOTP](https://mailgent.dev/two-factor): Generate time-based one-time codes and backup codes. - [Calendar](https://mailgent.dev/calendar): Create events, manage availability, share iCal. - [Identity (DID)](https://mailgent.dev/identity): did:web identity with an Ed25519 signing key. - [USDC wallet](https://mailgent.dev/wallet): Funded wallet on Base, x402 pay-per-call under mandates. - [MCP server](https://mailgent.dev/mcp): Every capability as scope-gated MCP tools. ## Pricing - [Pricing](https://mailgent.dev/pricing): Free, Developer ($19/mo), Startup ($199/mo), Enterprise. ## Use cases - [Give your assistant agent an inbox and calendar.](https://mailgent.dev/use-cases/personal-assistant): Give your AI personal assistant a real inbox and calendar. Triage email, draft and send replies, and manage your schedule over a clean API or MCP. - [Give your finance agent its own wallet.](https://mailgent.dev/use-cases/finance-ops-agent): Give your finance-ops agent an inbox for statements, a vault for credentials, and a USDC wallet for payouts. Reconcile and pay under mandates over API or MCP. - [Give your QA agent a real inbox.](https://mailgent.dev/use-cases/qa-testing-agent): Give your QA agent a real inbox and TOTP. Receive verification emails, read 2FA codes, complete password resets, and test full signup flows over API or MCP. - [Give your research agent an identity.](https://mailgent.dev/use-cases/research-agent): Give your AI research agent a real inbox and a did:web identity. Sign up for data sources, receive verification links, and pay per-call for paywalled APIs. - [Give your support agent an inbox.](https://mailgent.dev/use-cases/customer-support-agent): Give your AI support agent a real inbox at name@mailgent.dev. Receive tickets, reply in-thread, attach files, and escalate over a clean API or MCP. - [Let your community agent reply for you.](https://mailgent.dev/use-cases/community-manager-agent): Give your AI community agent a real inbox. Field member questions, answer FAQs in-thread, and route the rest to your team over a clean API or MCP. - [Let your procurement agent pay invoices.](https://mailgent.dev/use-cases/procurement-agent): Give your procurement agent an inbox for invoices and a USDC wallet to settle them. Read, verify, and pay under spending mandates over a clean API or MCP. - [Let your recruiting agent email candidates.](https://mailgent.dev/use-cases/recruiting-agent): Give your AI recruiting agent a real inbox. Reach out to candidates, read replies in-thread, schedule interviews on a calendar, and keep every message logged. - [Let your scheduling assistant run the calendar.](https://mailgent.dev/use-cases/scheduling-assistant): Give your AI scheduling agent an inbox and calendar. Negotiate times over email, create events, manage availability, and share an iCal feed over API or MCP. - [Let your travel agent book and confirm.](https://mailgent.dev/use-cases/travel-booking-agent): Give your AI travel agent an inbox for confirmations, a calendar for the trip, and a USDC wallet to pay. Book flights, hotels, and meetings over API or MCP. - [Put your sales agent in the inbox.](https://mailgent.dev/use-cases/sales-outreach-agent): Give your AI sales agent a verified inbox. Send outreach, catch replies in-thread, follow up, and book demos over a clean API or MCP — with DKIM deliverability. - [Route on-call alerts to your agent.](https://mailgent.dev/use-cases/devops-oncall-agent): Give your on-call agent an inbox for alert emails and a vault for the keys it needs. Triage, acknowledge, and remediate incidents over a clean API or MCP. ## Integrations - [Mailgent for Claude](https://mailgent.dev/integrations/claude): Connect Mailgent to Claude over MCP. Claude gets a real inbox at name@mailgent.dev plus vault, 2FA, calendar, identity, and wallet tools, gated by scopes. - [Mailgent for Cohere](https://mailgent.dev/integrations/cohere): Add Mailgent to a Cohere agent via tool use. Your Command-model agent gets a real inbox, vault, and identity to send email and act under scoped permissions. - [Mailgent for CrewAI](https://mailgent.dev/integrations/crewai): Add Mailgent to CrewAI so each crew member gets its own inbox and identity. Agents email, store secrets, clear 2FA, and act as distinct, scoped, accountable actors. - [Mailgent for Cursor](https://mailgent.dev/integrations/cursor): Connect Mailgent to Cursor over MCP. Your coding agent gets a real inbox, vault, and TOTP tools — ideal for testing email verification and 2FA flows from the editor. - [Mailgent for Gemini](https://mailgent.dev/integrations/gemini): Give your Gemini agent a real inbox and identity. Declare Mailgent actions as function-calling tools so Gemini can send email, manage secrets, and act under its identity. - [Mailgent for Goose](https://mailgent.dev/integrations/goose): Connect Mailgent to Goose, the open-source MCP agent. Goose gains a real inbox, vault, 2FA, calendar, identity, and wallet tools, all scope-gated to the agent key. - [Mailgent for Haystack](https://mailgent.dev/integrations/haystack): Integrate Mailgent into Haystack pipelines as tools or a custom component. Your agentic pipeline can email results, manage secrets, and act under its own identity. - [Mailgent for LangChain](https://mailgent.dev/integrations/langchain): Give your LangChain agent a real inbox and identity. Wrap Mailgent as tools for chains, agents, and LangGraph, or connect via MCP for mail, vault, 2FA, and payments. - [Mailgent for LlamaIndex](https://mailgent.dev/integrations/llamaindex): Add Mailgent to your LlamaIndex agent as FunctionTools. Your data agent gets a real inbox, vault, and identity to email results and act on retrieved information. - [Mailgent for Make](https://mailgent.dev/integrations/make): Use Mailgent in Make (Integromat) scenarios via the HTTP module. Send and read agent email, manage secrets, and pay per call inside your visual automations. - [Mailgent for n8n](https://mailgent.dev/integrations/n8n): Call Mailgent from n8n with the HTTP Request node. Trigger on inbound agent email, send replies, manage secrets, and pay per call inside your automation workflows. - [Mailgent for Ollama](https://mailgent.dev/integrations/ollama): Pair Mailgent with Ollama tool-calling models. Your locally-run agent gets a real inbox and identity to send email, hold secrets, and act, while the model stays on your machine. - [Mailgent for OpenAI](https://mailgent.dev/integrations/openai): Give your OpenAI agent a real inbox and identity. Expose Mailgent as function tools or connect over MCP for mail, vault, 2FA, calendar, and wallet capabilities. - [Mailgent for Perplexity](https://mailgent.dev/integrations/perplexity): Combine Perplexity's answers with Mailgent's inbox and identity. A research agent can email findings, sign up for sources, and act, with verification and payments handled. - [Mailgent for the Vercel AI SDK](https://mailgent.dev/integrations/vercel): Add Mailgent to the Vercel AI SDK. Define mail, vault, and identity tools with tool() and let your streaming agent send email and act under its own identity. ## Compare - [Mailgent vs Amazon SES](https://mailgent.dev/vs/mailgent-vs-amazon-ses): Amazon SES sends and receives email at scale but gives an agent no identity, vault, 2FA, or inbox tooling. See how Mailgent compares for AI agent use cases. - [Mailgent vs building it yourself](https://mailgent.dev/vs/mailgent-vs-build-it-yourself): Building agent identity means integrating email, secrets, 2FA, calendar, DIDs, and a wallet yourself. See the real cost versus one Mailgent signup call. - [Mailgent vs the Gmail API](https://mailgent.dev/vs/mailgent-vs-gmail-api): The Gmail API lets an agent drive a Google mailbox, but it's bound to a human account, OAuth, and policy not built for agents. See how a purpose-built agent inbox compares. - [Mailgent vs Mailgun](https://mailgent.dev/vs/mailgent-vs-mailgun): Mailgun is an email API for sending, receiving, and routing at scale. Mailgent gives AI agents an inbox plus identity, vault, 2FA, and payments. Compare for agent use. - [Mailgent vs Postmark](https://mailgent.dev/vs/mailgent-vs-postmark): Postmark delivers transactional email fast and reliably. Mailgent gives an AI agent its own inbox, identity, vault, 2FA, and wallet. Compare the two for agent use cases. - [Mailgent vs a shared inbox](https://mailgent.dev/vs/mailgent-vs-shared-inbox): Sharing a team inbox with an AI agent breaks attribution, scoping, and security. See why a per-agent identity with its own address and scoped key is the better model. ## Glossary - [Agent email address](https://mailgent.dev/glossary/agent-email-address): An agent email address is the deliverable address assigned to an AI agent, such as name-id@mailgent.dev, used to send and receive mail programmatically with full authentication. - [Agent identity](https://mailgent.dev/glossary/agent-identity): Agent identity is the verifiable, persistent set of credentials — a DID, signing keys, and an email address — that lets an AI agent prove who it is and act accountably. - [Agent inbox](https://mailgent.dev/glossary/agent-inbox): An agent inbox is a real email address an AI agent owns and operates programmatically — sending, receiving, and acting on mail over an API or MCP instead of a mail client. - [Decentralized identifier (DID)](https://mailgent.dev/glossary/decentralized-identifier): A decentralized identifier (DID) is a globally unique, self-controlled identifier that resolves to a document of public keys and services — the basis of verifiable agent identity. - [did:web](https://mailgent.dev/glossary/did-web): did:web is a DID method that ties a decentralized identifier to a domain, resolving to a DID document served over HTTPS — a simple, verifiable identity anchor for AI agents. - [DKIM](https://mailgent.dev/glossary/dkim): DKIM (DomainKeys Identified Mail) signs outgoing email so receivers can verify the sender domain and detect tampering. It's a key reason agent mail lands in the inbox. - [Ed25519](https://mailgent.dev/glossary/ed25519): Ed25519 is a fast, secure elliptic-curve signature scheme. It's the keypair an AI agent uses to sign requests and prove control of its did:web identity. - [Model Context Protocol (MCP)](https://mailgent.dev/glossary/mcp): MCP is an open protocol that lets AI models call external tools and data through a standard interface. Mailgent exposes mail, vault, 2FA, calendar, and payments as MCP tools. - [Spending mandate](https://mailgent.dev/glossary/spending-mandate): A spending mandate is the rule set that limits what an agent's wallet can spend: per-transaction caps, daily totals, and allowlists, enforced at the wallet rather than the prompt. - [TOTP](https://mailgent.dev/glossary/totp): TOTP (time-based one-time password) is the rotating six-digit code authenticator apps produce from a shared secret and the clock. Mailgent's vault generates them for agents. - [Verifiable credential](https://mailgent.dev/glossary/verifiable-credential): A verifiable credential is a cryptographically signed, tamper-evident claim about a subject that anyone can verify independently — a building block for trusted agent identity. - [x402](https://mailgent.dev/glossary/x402): x402 uses the HTTP 402 Payment Required status to let a server charge per request. Agents pay in stablecoin per call — no accounts, no API keys, settle on-chain in seconds. ## Blog - [Introducing Mailgent: give your AI agent an inbox](https://mailgent.dev/blog/introducing-mailgent): Email and identity for AI agents — a real address, a vault, 2FA, a calendar, a verifiable identity, and a wallet, all from one API call. - [Why AI agents need a real identity](https://mailgent.dev/blog/why-agents-need-identity): Anonymous agents can't be trusted, scoped, or audited. A verifiable identity is what lets you safely hand an agent the keys to act. - [Email is the interface agents already have](https://mailgent.dev/blog/email-is-the-agent-interface): Every service speaks email. Give an agent an inbox and it can sign up, verify, receive, and reply — no custom integration per provider.