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.
Settlement only happens after a route's response is already decided, and only if that response succeeded, which makes every failed call free, on purpose.
Stripped of the hype, agentic commerce means one specific thing: software deciding, on its own, whether an action is worth its price, and paying for it inline.
The honest answer depends on the path: one cent for a direct drafted send, three cents if you want to preview the draft first. Here is the full arithmetic.
HTTP reserved a status code for pricing a response inline thirty years before any rail could settle that price fast enough to matter.
Seats assume one human per account. Agents don't map onto that unit at all, which is why DimeBox's core product has neither seats nor a subscription.
A cost of zero carries no signal. Even a one-cent price per call gives a system something free and flat-rate pricing both fail to provide.
Seat-based budgeting doesn't apply to agents. Per-call prices and wallet-level spend limits are the actual tools for controlling a fleet's spend.
A free or one-dollar inbox is the visible price. The real cost of an agent's email identity is everything it drafts, sends, and receives afterward.
Cent-level payments never worked when a human had to approve each one. Machines do not experience checkout friction, and that is the whole difference.
Subscriptions assume a human deciding whether a tool is worth a monthly fee. Agents decide per call instead, and that calls for a different pricing model entirely.
From a card charge on Stripe Checkout to a debited ledger entry on a paid API call - the complete path a DimeBox wallet takes, start to finish.
A wallet_secret authenticates your agent's calls. Linking the same wallet to an account gives a human a separate, login-based way to manage it.
A declined card can hit a wallet at creation, at top-up, or mid-auto-reload. None of those are the same failure, and none of them should be handled the same way.
Creating a DimeBox wallet the default way carries a one-time setup fee. Choosing the monthly subscription option instead skips it entirely.
A wallet_secret is the one credential that can spend a DimeBox wallet's balance. It's shown once. Here's why that design choice is deliberate, not an oversight.
Fund a DimeBox wallet with a one-time card charge whenever you need to, or skip the setup fee with a recurring monthly subscription. Here's how to pick.
A card-funded wallet with no human reviewing each charge needs a ceiling that isn't just "however much is in the balance." Daily spend limits are that ceiling.
An agent mid-loop doesn't get to pause and go find a credit card. Auto-reload tops a DimeBox wallet back up off a saved card before the balance hits zero.
A DimeBox wallet isn't a crypto wallet or a bank account - it's a closed-loop balance you fund by card and spend down one priced API call at a time.
x402 assumes a wallet that can sign USDC payments on Base. A card-funded DimeBox wallet authenticates the same paid calls with a bearer secret instead - no signing, no chain.