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.
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.