Billing and spend cap

There is no free tier. Plans are billed monthly with a number of included checks. The current plans and prices are on the pricing page; this page describes how limits behave.

A check is one verification (siteverify or one assessment, whatever it scores). Only checks in the active or grace states count toward usage.

State	What happens
active	Full service.
grace	Paid but past due, or over the included checks inside the grace window. Full service.
restricted	A plan that was paid and then lapsed or reached its usage cap. Pass-through with no scoring: siteverify answers success: true, score: 0.5 with PLAN_RESTRICTED; assessments answer 402 plan-restricted.
inactive	Never paid, or restricted for too long. Siteverify answers success: false with plan-required.

A restricted answer carries a score of 0.5, so code that gates on success alone passes people through, and code that gates on the score decides for itself.

Spend cap

An account can have a spend cap on: no charges beyond the plan. With it on, an account that uses up its included checks is restricted (reason quota) instead of being billed overage, so a traffic spike cannot become a surprise bill. With it off, checks beyond the included amount are billed as overage per check at the rate on the pricing page. At launch the cap is set by RevokeGPT for your account; there is no self-service switch yet.

Local development

An inactive account is served normally for loopback hostnames only (localhost, 127.0.0.1, [::1]), capped at 500 checks per UTC day. It is a development aid, not a free tier.