agentmbox – Pay-Per-Use Email for AI Agents

TL;DR

TL;DR: agentmbox is a pay-per-use email service where AI agents get their own inbox by paying with a crypto wallet via the x402 protocol — no sign-up, no API keys, no credit card required.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: agentmbox.com
• License: Proprietary (no open-source license detected)
• HN launch thread: Not found on the product page

What Is agentmbox?

agentmbox is an email service designed specifically for AI agents. Instead of humans signing up and managing credentials, the agent itself pays for email operations using its own crypto wallet through the x402 protocol — a standard that lets HTTP requests carry payment in the header.

The core proposition:

• No sign-up, no API key, no credit card — the wallet is the identity
• Mailbox auto-provisions on first payment
• Pricing is granular and per-operation

Pricing (verified from agentmbox.com):

| Operation | Cost | |---|---| | Create mailbox | $0.50 | | Send email | $0.005 | | Get email (by ID) | $0.001 | | Extract OTP | $0.005 | | Extract text (HTML-to-text) | $0.003 | | List emails | Free | | Delete email | Free |

New agents get $10 in free API credits to start. Payment runs over USDC on Solana or Base (EVM-compatible).

Setup Workflow

Step 1: Point Your Agent at llm.txt

Every agent discovers the full API surface automatically by reading https://agentmbox.com/llm.txt. This file contains the endpoint definitions, auth flow, and current pricing — no documentation hunting required.

# Example: fetch the API manifest
curl https://agentmbox.com/llm.txt

Step 2: Set Up a Wallet (or Use the Onboarding Credits)

If your agent already has a wallet with USDC on Solana or Base, skip this. If not, agentmbox offers $10 in free credits via a standard API key flow — claim them at the onboarding page.

Step 3: Create a Mailbox

Your agent pays $0.50 via x402 to provision its inbox. The address is derived from the wallet public key — no form, no confirmation screen.

POST /v1/mailbox
x402: Pay-Request: USDC.solana:<amount>

Response includes the inbox address (e.g. [email protected]).

Step 4: Send and Receive Email

# Send an email ($0.005)
POST /v1/send
x402: Pay-Request: USDC.solana:0.005

# Get an email by ID ($0.001)
GET /v1/emails/<id>
x402: Pay-Request: USDC.solana:0.001

# Extract OTP from an email ($0.005)
POST /v1/extract-otp/<email-id>
x402: Pay-Request: USDC.solana:0.005

Deeper Analysis

Why x402 Matters

Most API services authenticate with an API key in a header. x402 moves payment into the HTTP layer itself — the Pay-Request header carries a signed intent to pay, and the server responds with the resource only after payment clears. This removes the need for:

• User accounts and session management
• API key issuance and rotation
• Stripe/billing infrastructure on the server side

For agents that need email (OTP verification, newsletters, transactional alerts), this is a cleaner fit than the traditional “create an account and hope the API key stays secret” model.

Custom Domain Support

For $0.50, you can attach your own domain with SPF, DKIM, and DMARC configured — useful for agents that need to send from a recognizable address rather than @agentmbox.com.

Competitive Landscape

The closest alternative is receiving a dedicated email address through a traditional email API (SendGrid, Mailgun), which requires account creation and typically bills per-thousand-emails. agentmbox is operation-granular: you pay only for what the agent uses, nothing per-seat.

Practical Evaluation Checklist

• x402 protocol support — confirmed (Solana + Base USDC)
• No sign-up required — wallet IS the identity
• Free credits for new agents — $10 via onboarding flow
• OTP extraction — built-in, $0.005 per extraction
• Custom domain — available, $0.50 one-time
• No open-source license — proprietary SaaS

Security Notes

• x402 payment flow uses signed intents — the mailbox address is derived from the wallet public key, making it self-certifying
• SPF, DKIM, DMARC on custom domains reduces email bouncing
• No API key storage on the server side (wallet-based identity)
• $10 free credits require an API key onboarding flow — treat this key like any other secret

FAQ

Q: Does agentmbox work with any blockchain? A: Currently USDC on Solana and Base (EVM). The x402 spec is chain-agnostic, so more chains may be added.

Q: What happens if the agent runs out of funds? A: The mailbox stays active, but subsequent operations fail with a payment required error. You can top up via the dashboard or by sending USDC to the wallet.

Q: Can a human use agentmbox, or is it agent-only? A: Humans can use it via the free credits onboarding, but the product is designed for agents — the UX is API-first, not UI-first.

Q: Is there a free tier for low-volume agents? A: $10 in credits is the starting point. Listing and deleting emails is free. For persistent use, you fund the wallet.

Conclusion

agentmbox solves a specific problem: how do you give an AI agent an email identity without building account infrastructure? By using the wallet-as-identity model with per-operation micro-payments via x402, it removes the human bottleneck from email provisioning. If your agent workflow involves OTP verification, email-triggered actions, or transactional alerts, this is a cleaner primitive than spinning up a SendGrid account and managing API keys.

For runany.dev’s audience — developers building with AI agents — this is worth a look.