Introduction

AI agents need their own identity — a wallet, an inbox, a vault, a calendar, a signing key — and they need to pay for things. The internet wasn't built for them. Mailgent is.

Equip an agent

One Mailgent project bundles everything an agent needs to operate, behind a single API key:

• Wallet — a USDC smart account on Base. Pay any x402-priced URL or MCP tool under your spend caps; the agent never holds a private key.
• Inbox — a real <slug>@mailgent.dev address. Send and receive, sign up to third-party SaaS.
• Vault — per-credential AES-256-GCM storage with TOTP.
• Calendar — read/write events, optional public iCal URL.
• DID — a did:web Ed25519 keypair for signing and verifying.

curl -X POST https://api.mailgent.dev/v0/agent-signup -d '{}'
# → { "platform_key": "mgpk-…", "identity": { "rawKey": "mgnt-…", ... } }

→ For Agents — agent self-signup, one curl. → For Humans — same thing via the Console.

Here's an agent paying an x402 endpoint in one call:

const paid = await mailgent.payments.pay({ url: "https://api.example.com/search" });
console.log(paid.content, paid.txHash);

How the pieces fit

Every API key belongs to a Project. Every Project belongs to an Org (your workspace and billing container). That's the whole shape.

Want to accept x402 payments / sell to agents? That's a separate product at loomal.ai.

Where to go next

• Wiring up an agent? → For Agents or For Humans
• Paying for tools? → Pay for tools
• Want the deeper model? → Concepts covers payments architecture, scopes, mandates, and the key tiers.