Blog

Email for agents.

How AI agents get a real inbox, pay per call instead of by the seat, and send and receive email without a human in the loop. Guides, comparisons, and deep dives from the team building DimeBox.

All posts Agent Inbox Fundamentals Agentic Commerce Economics Comparisons & Alternatives Conceptual & Industry Pieces Framework & Tooling Integration Guides Receiving & Processing Inbound Email Security, Trust & Abuse Prevention Sending & Drafting Email With AI Agents Wallets & Card-Funded Payments x402 & HTTP 402 Fundamentals

Is x402 Secure? A Developer's Threat Model for Pay-Per-Call APIs

Replay protection, facilitator trust, and what happens when a call fails partway — a working threat model for pay-per-call APIs, not a yes/no answer.

Base Sepolia vs Base Mainnet: Testing Agent Payments Safely

Testing x402 payments against real USDC costs real money on every mistake. Base Sepolia runs the same protocol with test tokens that don't.

x402 Facilitators Explained: Who Verifies and Settles Your Payment

A signed payment isn't money moved yet. A facilitator verifies it and submits it on-chain — a job deliberately kept separate from the API server.

Gasless Payments for Agents: What EIP-3009 Actually Does

EIP-3009 lets an agent sign a USDC payment without holding a separate gas token at all — here's what the signature actually contains.

The exact Scheme Explained: x402's Default Payment Method

x402's default payment method pays the exact quoted amount for the exact request that triggered it — no running balance, no invoice, no tip jar.

USDC on Base: Why DimeBox Settles Payments Here

Why DimeBox prices every call in USDC and settles on Base specifically, not any stablecoin on any chain.

How a 402 Payment Required Response Actually Works, Step by Step

What's actually inside a 402 response, what a client has to build in reply, and what a server checks before it runs the route — walked through stage by stage.

x402 vs API Keys: Why Agents Need a Different Auth Model

API keys answer who's calling. x402 answers whether this specific call got paid for — a narrower question that fits an autonomous caller better.

Why HTTP 402 Sat Unused for 30 Years — and Why That's Changing

HTTP reserved a status code for payment in 1997. It took cheap stablecoin settlement and machine callers with no use for a checkout page to finally use it.

What Is x402? The HTTP 402 Payment Protocol Explained

x402 turns the long-unused HTTP 402 status code into a working payment handshake: call an endpoint, get asked to pay, sign a payment, get your response.