The basic rule
1 page crawled = 1 token. Only successful HTML pages consume tokens. Failed crawls, 4xx and 5xx responses, robots-blocked pages, and non-HTML resources (images, scripts, fonts) do not count against your token balance.
What also uses tokens
Beyond crawling, AI tasks consume tokens based on the work involved:
Brand Kit Auto Import: roughly 12 tokens.
AI Recommendations: estimate shown before generation, varies by Fast or Slow mode and the number of pages in scope.
Migration Assistant validation: roughly 45 tokens per validation.
Migration AI Recommendations: roughly 120 tokens.
Fix proposals: roughly 15 tokens.
Custom test runs: estimate shown after the Judge Agent dry-run.
What does NOT use tokens
Browsing the dashboard, viewing reports, opening any settings page.
Sharing or exporting reports.
Receiving alerts, webhooks, or integration messages.
Scheduling a scan (only running it consumes tokens).
Where to see your balance
Three places: the org chip top-left shows X/Y next to "(buy tokens)"; the user dropdown shows "Tokens used: X/Y" with a Top up button; the project Overview has a Tokens widget.
Buy more tokens
Click Top up (in the user dropdown) or buy tokens (in the org chip). Stripe handles the purchase. Tokens you buy this way are added to your balance and do not expire.
What happens when you run out
Scheduled and continuous scans pause until your next billing cycle or until you top up. Manual scans fail with a clear error. AI features show the token shortfall in their estimate modals.