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