Mailgent icon

Mailgent

Mailgent provides email and identity infrastructure for AI agents, including a real inbox, encrypted vault, calendar, DID, and USDC wallet. It is built for developers who want agents to provision once and then operate through scoped API, MCP, CLI, or SDK tools.

Mailgent

Email and identity infrastructure for AI agents

Mailgent is an email and identity service for AI agents. It provisions a complete agent identity in one API call, combining a real inbox, encrypted vault, calendar, DID, and USDC wallet so software can operate with a persistent presence instead of ad hoc keys and prompts.

The product is built around a scope-gated workflow: an agent is provisioned, connected through MCP, CLI, or SDK, and then uses ready-made tools to read and send mail, store and retrieve secrets, generate 2FA codes, book time, sign requests, and pay for API usage when needed.

Core capabilities

Deliverable email inbox

Each agent gets a real address at [email protected] and can send, receive, thread, and label mail over API or MCP, with DKIM and verified senders called out on the mail page.

Encrypted credential storage

Store API keys, tokens, login credentials, and backup codes in an encrypted vault that retrieves secrets per scope and keeps plaintext out of logs.

Built-in 2FA / TOTP

Generate time-based one-time codes on demand from a seed stored in the vault, including backup-code handling for accounts that require 2FA.

Calendar actions

Create events, manage availability, and share an iCal feed so an agent can coordinate scheduling through the calendar capability.

DID identity and signing

Assign each identity a did:web identity with an Ed25519 keypair so the agent can sign requests and prove who it is.

Agent wallet for payments

Fund a USDC wallet on Base so agents can pay x402-priced URLs under spending mandates set by the user.

Practical use cases

  • Agent email handling

    Give an agent a real inbox so it can handle confirmations, receipts, replies, and other email-based workflows without scraping a UI or relying on IMAP.

  • Secret management for autonomous workflows

    Store API keys, tokens, logins, and backup codes in the encrypted vault, then retrieve them only when a task requires access.

  • 2FA-gated logins

    Let an agent clear 2FA prompts by generating live TOTP codes from a seed kept in the vault, including recovery-code workflows where needed.

  • Scheduling and coordination

    Use the calendar capability for scheduling tasks such as event creation, availability management, and sharing an iCal feed with other systems or people.

  • Verifiable agent identity

    Assign a DID and signing key to an agent so it can prove its identity when interacting with services or signing requests in a controlled way.

Pros and Cons

Pros

  • Combines email, vault, calendar, identity, and payments in a single provisioning flow.
  • Supports agent-native access through MCP, REST, CLI, and SDK interfaces.
  • Uses scope-gated tools and per-identity keys so access is limited by capability.
  • Includes built-in support for 2FA/TOTP workflows and backup codes.
  • Pricing scales by agent identities and usage rather than per-seat licensing.

Cons

  • The public pages do not yet document every integration or supported external system in detail.
  • Some capabilities and limits are plan-dependent, but the source only explains the broad tier structure rather than every operational boundary.

FAQ

How does setup work?

Mailgent provisions an identity in one API call. The result includes a real email address, DID and signing key, encrypted vault, calendar, and a USDC wallet; these can then be connected through the MCP server, CLI, or SDK.

Can Mailgent be used for teams or fleets of agents?

The pricing page shows plan tiers that scale from a Free plan to Developer, Startup, and Enterprise. It also says agents are provisioned as identities rather than seats, and higher plans add features such as a funded USDC wallet, spend mandates, audit logs, and SSO/SAML.

How do agents interact with the product after provisioning?

Mailgent is built around a clean API, MCP access, and a CLI/SDK. The site says it can be hosted at api.mailgent.dev/mcp or run locally, and it exposes tools such as mail_send, vault_store, calendar_create, and identity_sign.

What systems or integrations are supported?

Mailgent’s published materials emphasize email, encrypted secrets, TOTP codes, calendar actions, DID identity, and USDC wallet payments. The source does not list broader third-party integrations beyond MCP, REST, CLI, and SDK access.

Quick Facts

Category
Developer Tool
Primary use
Email and identity infrastructure for AI agents
Access methods
API, MCP, CLI, SDK
Source domain
mailgent.dev
Pricing model
Free tier plus paid plans
Notable workflow
Provision an identity, connect it, then operate with scoped tools