PRODUCT · BILLING

Wallets you top up, calls users make direct.

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.

Get started — free
WALLET · user_28f3a · pro tier
$5.80balance
62% of $10/day budgetresets in 6h 12m
gpt-4o · 1.2k tok−$0.018
claude · 890 tok−$0.012
github.create_issue−$0.001
stripe top-up+$10.00
/billing

Billing

Per-user wallets you top up via API. Plus client-side calling — end users hit Assistiv directly.

  • Wallets
  • Top-ups
  • Refunds
  • Pre-flight
  • Holds
  • Tier budgets
$2.4Mtracked monthly
840kwallets opened
99.95%ledger uptime
12 msp50 pre-flight
What it does

The three things billing actually does.

WALLETS

You top up, we debit.

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.

wallets · ok
→ per-user wallets
200 · 99.95%
CLIENT-SIDE

End users call Assistiv directly.

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.

client-side · ok
→ client-side calling
200 · 99.95%
RECONCILED

Tokens, tools, agents — same wallet.

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.

reconciled · ok
→ refunds + holds
200 · 99.95%

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.

Why we built this

Urgent backstory

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.

Use it for

Four common
ways teams ship with Billing.

01P

Per-user wallets

One wallet per signup. Top up via API after any payment flow you run. Debits are atomic, audit-logged, concurrency-safe.

02C

Client-side calling

End users call api.assistiv.ai directly with their sk-eu_ key. No proxy server. Streaming works out of the box.

03R

Refunds + holds

Reverse a charge with one API call. Hold against streaming jobs. Manual adjustments are first-class, not a hack.

04H

Hosted receipts

Branded statement page for end users. CSV export. Per-user, per-month rollups.

How it works

Four steps, ten minutes.

1

Create end-user

endUsers.create({ id: "u_28f3a" })
2

Top up via API

wallets.topUp({ user, amount })
3

Pass user on calls

client.chat({ user: "u_28f3a", ... })
4

Auto-debit on settle

Tokens, tools, agents — all reconciled
It works with

The stack you already have.

Stripe
Lago
Orb
Paddle
Plaid
Braintree
Adyen
Recurly
“

Wallets shipped Friday. Charged users by Monday. We deleted ~900 lines of Stripe glue.

— Aleks · founder, Drafthub
D
Pricing

Free to ship. Pay when you scale.

FREE$0

Up to 1k requests/mo. Every product included.

Start free →
SCALE$0.0008

per request, after free tier. No markup on tokens. Cancel anytime.

What's next

Shipping this quarter.

Read full changelog →
WK 12Multi-currency
WK 13Refund webhooks v2
WK 14Saved-card vault UI
WK 15Quarterly statements
ONE AFTERNOON AWAY

Ship per-user billing this afternoon.

We onboard 1–2 indie startups a week. If you'd rather ship features than maintain a billing stack, talk to us.

Get started — free