Billing & Tokens
How Drizz meters test runs in DT, what drives the cost of a step, what each wallet state means, and how to top up.
Drizz meters usage in DT (Drizz Tokens), deducted per test step from a single wallet shared by the organization.
Unit
DT (Drizz Tokens), deducted per step
What drives cost
How the step was resolved — Cached lowest, AI highest
Billing event
One per step, regardless of retries
Wallet
One shared balance per organization
Watch out
An exhausted wallet surfaces as a server error — check the balance before debugging
Prerequisites
Drizz organization account
Access to the organization billing page
A payment card, for top-ups
How a step is metered
Every step falls into one of four categories. The first signal wins. Each step is billed once, even if it retried.
Cached
Drizz has resolved this step on this screen before
Lowest
System
A system command, or a navigation step
Low
OCR
Resolved by reading text on screen
Moderate
AI
Vision AI ran to locate the element
Highest
Cache coverage builds across runs, so the DT cost of a test plan falls as it is re-run. See Caching.
Per-category DT rates and the DT-to-currency rate are shown on your organization's billing page, which is authoritative. They are not repeated here because they change.
Where to see usage
Wallet badge, desktop app header
Current organization balance
Run banner
DT used by the run in progress
Report
DT used, for a finished run
Organization billing page
Balance, history, current rates, top-ups
The wallet badge can show a stale balance after a top-up. Navigate away and back to refresh it.
Wallet states
Healthy
Normal balance
Runs start as expected
Low
Balance running down
Runs start. Top up before it blocks a release
Blocked
No credit remaining
Runs will not start
A blocked wallet does not always report itself as a billing error. It surfaces as a server error, an availability error, or a run that does not start.
Top up
Open your organization's billing page.
Select top-up.
Pay by card.
Confirm the wallet badge shows the new balance. Navigate away and back if it is stale.
The balance is shared, so a top-up by any member unblocks every member.
Enterprise accounts can be configured to allow runs to continue past a zero balance. Ask your Drizz contact.
Common mistakes
Compared cost across two runs of a new plan
Cache coverage differs between runs — early runs cost more
Debugged a "server error" before checking the balance
An empty wallet surfaces as an unrelated-looking failure
Assumed the wallet is per-user
It is shared org-wide. Another member's regression run drains it
Quoted a DT rate from a document or a deck
Rates change. Read them from the billing page
Next
Organizations & access — why the wallet is shared
Caching — how steps become cheap
Reading a report — per-run usage
Last updated: 6 August 2026
Last updated
Was this helpful?