You handle payments your way and call our API to top up. We debit per token, per tool, per request. End users can also call Assistiv directly — no server hop, no proxy code, their wallet still pays.
Per-user wallets you top up via API. Plus client-side calling — end users hit Assistiv directly.
Bring any payment processor — Stripe, Paddle, invoicing. Call walletTopUp() to credit the end-user. We debit per token, per tool, per request. Atomic. Audit-logged.
Issue an sk-eu_ key per end-user. Their browser/app calls api.assistiv.ai with it — no proxy through your server, no streaming code to write. Their wallet still pays.
Estimate up front, hold the cost, settle when the job finishes. Streaming, batches, tool-chains, MCP calls all reconcile to the cent against one wallet.
Hand-rolling a wallet table with row locks, atomic debits across streaming + tools, refund/hold flows, and concurrency-safe top-ups is a six-week project. We did it once. You can have it.
We watched five AI startups in a row hand-roll the same billing stack — and burn three weeks doing it. We packaged ours so you don't have to. Drop the SDK in once; this product, plus the rest of the suite, comes with it.
One wallet per signup. Top up via API after any payment flow you run. Debits are atomic, audit-logged, concurrency-safe.
End users call api.assistiv.ai directly with their sk-eu_ key. No proxy server. Streaming works out of the box.
Reverse a charge with one API call. Hold against streaming jobs. Manual adjustments are first-class, not a hack.
Branded statement page for end users. CSV export. Per-user, per-month rollups.
endUsers.create({ id: "u_28f3a" })wallets.topUp({ user, amount })client.chat({ user: "u_28f3a", ... })Tokens, tools, agents — all reconciled
Wallets shipped Friday. Charged users by Monday. We deleted ~900 lines of Stripe glue.
— Aleks · founder, Drafthubper request, after free tier. No markup on tokens. Cancel anytime.
We onboard 1–2 indie startups a week. If you'd rather ship features than maintain a billing stack, talk to us.