Metered on probes and challenges.
A probe is one measured browser session. A challenge is one ceremony minted, by the widget or by the API. Identifiers come with every probe. Nothing else is counted.
| Plan | Monthly | Probes | Challenges |
|---|---|---|---|
| Sandbox | Free | 1,000 | 100 |
| Signal | $250 | 10,000 | 1,000 |
| Anomaly | $750 | 25,000 | 2,500 |
| Incursion | $3,500 | 100,000 | 10,000 |
| Scale | $12,500 | 1,000,000 | 100,000 |
| Enterprise | Contact us | Unmetered | Unmetered |
Overage on a paid plan: $0.0025 per probe, $0.025 per challenge.
What you get on every plan
There is no feature ladder. The Sandbox tier runs the same sensor, the same ruleset and the same API as Enterprise, and returns the same fields. What the plans change is how many sessions you may measure in a month.
Every probe returns the verdict, every finding under a stable ID with its tier, the network and concealment fields, the client session record the sensor built, and two device identifiers scoped to your site key. Every challenge returns its outcome, the step it reached, and the devices it ruled on.
How a probe is counted
A probe is counted at the moment the sensor resolves your site, which is when the browser session opens. That is deliberate. Counting at the verdict would mean a session that refused to be measured cost nothing, and refusing to be measured would become the cheap path.
A challenge is counted when it is minted rather than when it completes, for the same reason. Abandonment is not free.
At the limit
Sandbox stops. The resolver answers 404 so no session opens, an API mint
answers 402, and the widget reports quota-exceeded. Service resumes
at the start of the next UTC month.
Paid plans keep serving. The excess is billed as overage at the rates above. Nothing is turned off mid-month.
Enterprise is unmetered.
This month's counts are on the Plan and usage page in the dashboard, and at GET /v1/usage, which reports used, limit, overage and overage in dollars per unit.
Questions
What counts as a probe?
One measured browser session. It is counted when the sensor resolves your site at session open, so a session that opens is a session you are charged for, whatever the verdict turns out to be.
What counts as a challenge?
One ceremony minted, by the widget or by the API. Minting is the charged event, not completion, so a ceremony a visitor abandons is still counted.
What happens at the plan limit?
Sandbox stops until the next UTC month: the sensor opens no sessions, a mint answers 402, and the widget reports quota-exceeded. Paid plans keep serving and bill the excess as overage. Enterprise is unmetered.
What does overage cost?
On a paid plan, $0.0025 per probe and $0.025 per challenge above the plan allowance.
Is there a contract or a minimum term?
No. Plans are monthly through Stripe, and you can change or cancel from the billing page in the dashboard.
Do device identifiers cost extra?
No. An instance identifier and a machine identifier come with every probe, scoped to your site key.
Run it against this browser.
The live probe measures the browser you are reading this in and shows the claims and the measurements side by side, with every finding it produced.