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.
Before pointing a funded signer at mainnet, run DimeBox's full provision-send-receive cycle against Base Sepolia, where a mistake costs nothing.
The Node quickstart's payment wrapper hides the actual signature. This post peels it back: the EIP-712 domain, the EIP-3009 message fields, and signing both with viem directly.
Hardcoding a price into an agent's code is a bug waiting to happen. Here's how to read DimeBox's live, authoritative prices instead of guessing.
DimeBox's OpenAPI spec generates a fully typed client in TypeScript or Python, but it knows nothing about payments — here's how the two layers fit together.
Adding email to a running agent loop means adding two actions with very different risk profiles — one free, one priced per call. Here's how to wire both in safely.
Not every agent needs to run forever. Here's how to build a cron-triggered job that polls a DimeBox inbox, tracks what it's already seen, and acts only on what's new.
A runnable Node.js walkthrough using @x402/fetch, @x402/evm, and viem to provision a DimeBox inbox, pay for a send, and read the reply back.
A runnable Python walkthrough of DimeBox's full x402 flow: install the SDK, register a signer, handle the 402-sign-retry loop, and provision and send from a real inbox.
There's no official CrewAI integration for DimeBox. Here's how to build a BaseTool subclass that lets one role in a crew send and read email, while every other role stays locked out.
LangChain has no official DimeBox package. Here's how to wrap the plain HTTP and x402 payment flow as two tools an agent can call: one free to read mail, one paid to send it.
No passwords to reset, no CAPTCHAs a script can't solve, no login — DimeBox's API is built around a caller that's a machine from the first request.
Draft, send, priority receive, and claim all cost different amounts and do different things — but every one of them runs through the exact same payment gate.
A DimeBox read token or wallet secret is shown exactly once because it's never stored in a form that could be shown again — only a one-way hash is.
DimeBox has no dedicated idempotency-key header — retry safety comes from charging only on success, nonce-bound signatures, and checking mailbox history before resending.
The clearest documented freeze-like control on DimeBox is the automatic, time-boxed cap every new wallet starts under — not a manual review process.
DimeBox doesn't store a payer-to-inbox link or per-message authentication results — so abuse response has to work at the credential layer instead.
DimeBox never records which wallet or address paid to create a given inbox — a privacy choice with real trade-offs for recovery and investigation.
Free inbox creation is throttled to 3 per day per IP — a blunt but necessary control in a system with no accounts to rate-limit against.
Random slugs, UUID message IDs, and strictly scoped lookups keep DimeBox inboxes from being discoverable by guesswork.
New DimeBox wallets are capped at $50 total balance and $10 of daily spend for their first few days — a built-in anti-fraud default, not a setting you configure.