Mermail: agent inbox and wallet for signup, codes, and pay

Mermail (mermail.app) gives an AI agent a private email identity and a user-controlled Agent Wallet so it can finish web errands: sign up, receive verification codes, pay, and keep receipts — without borrowing your personal Gmail or raw card.

Built by Nudgen-Marketing (nudgen.net· @nudgen_mkt). Public launch: Product Hunt · Mermail (Aug 15, 2026). Console: console.mermail.app. Docs: docs.mermail.app.

GitHub (Nudgen-Marketing)

Org: github.com/Nudgen-Marketing. Mermail-related public repos:

# CLI (until public npm publish)
npm install -g github:Nudgen-Marketing/mermail-cli
export MERMAIL_API_KEY="***"   # workspace-bound key from console

mermail doctor
mermail auth check
mermail mailboxes list --format table

# Prefer public_id from list; ensure reuses before provision
mermail mailboxes ensure \
  --email account-agent@mermail.app \
  --name "Account Agent" \
  --verification-mode \
  --idempotency-key account-agent-once

mermail emails list --mailbox-id MAILBOX_PUBLIC_ID --folder inbox --metadata-only
mermail wallet status --mailbox-id MAILBOX_PUBLIC_ID

Destructive CLI ops need --yes when non-interactive. Mailbox creation consumes provision credits — list/ensure first.

What you get

Control model (upstream docs): email side effects need explicit authorization. Payments stay inside PayBox policy — Mermail does not add a second approval layer.

Workflow

1. Create inbox — hosted Mermail address or custom domain
2. Connect AI — MCP, Agent Skill, or CLI
3. Optional payments — connect PayBox → Agent Wallet for funding, transfer/swap, x402 under your limits
4. Run errand — register → code from inbox → pay → archive receipt

Example use cases from product copy: buy domains under a cap, book services, pay small invoices, cancel subscriptions, vendor follow-ups, refund/support mail.

Hermes setup (Streamable HTTP + OAuth)

From mermail.app/integrations/hermes: interactive Hermes uses OAuth — do not put x-api-key on the interactive path. Use Streamable HTTP (POST), not SSE.

# ~/.hermes/config.yaml — merge under mcp_servers
mcp_servers:
  mermail:
    url: "<Mermail MCP Streamable HTTP URL from console>"
    auth: oauth
    # interactive: hermes mcp login mermail  (fresh terminal; OAuth needs >30s)

1. Copy MCP URL from Mermail console
2. Add server block; run hermes mcp login mermail in a new terminal (in-session reload often too short for OAuth)
3. Authorize on console.mermail.app, pick workspace; tokens cache under ~/.hermes/mcp-tokens/
4. hermes chat or /reload-mcp; try a mailbox list tool

Headless / jobs: drop auth: oauth, set headers.x-api-key: ${MERMAIL_API_KEY} from ~/.hermes/.env. Prefer MCP for interactive loops; CLI for batch JSON/JMESPath (non-interactive destructive flags need --yes).

Pricing (public site)

Confirm current numbers on the pricing page before budgeting.

When to use

Related on DevRels: agent payment patterns in pay.sh / x402 pieces — Mermail is the identity + OTP + wallet shell, not a replacement for every merchant API.

Links

• mermail.app
• GitHub · Nudgen-Marketing
• mermail-cli
• Docs
• Console
• Hermes integration
• @nudgen_mkt
• Product Hunt launch

Summary

Mermail wires agent email and PayBox Agent Wallet so agents can complete signup → verify → pay → receipt under your policy. Connect via MCP (OAuth for Hermes interactive; API key headless), scale from free single inbox to Developer multi-inbox, and keep payment authority in PayBox grants — not in the model prompt.