Plan defaults.
| Plan | Included credits | RPS | API keys | Response |
|---|---|---|---|---|
| Free | 100 | 1 | 1 | Summary |
| Basic | 10,000 | 2 | 1 | Summary |
| Pro | 75,000 | 5 | 3 | Full layer export available |
| Scale | 300,000 | 10 | 5 | Full layer export available |
| Business | 600,000 | 20 | 10 | Full layer export available |
| Enterprise | Custom | Custom | Custom | By contract |
Free credits reset on a UTC calendar-month schedule. Paid-plan credits follow the workspace's current Stripe subscription period. Entitlements can be reviewed manually for sensitive or high-volume access, and the dashboard and API enforce the active workspace state.
Additional credit packs.
Active paid workspaces can make a one-time Stripe purchase for additional credits without changing their subscription plan. Free workspaces are not eligible for credit packs.
| Pack | Credits | Price | Eligible plans | Limit per period |
|---|---|---|---|---|
| 10K Credit Boost | 10,000 | $25 | Basic, Pro, Scale, Business | 3 purchases |
| 50K Credit Boost | 50,000 | $79 | Pro, Scale, Business | 3 purchases |
| 200K Credit Boost | 200,000 | $249 | Scale, Business | 2 purchases |
Credit costs.
| Profile | Credits | Availability | Intended use |
|---|---|---|---|
quick | 1 | All plans | Lightweight screening and the default for new requests. |
standard | 3 | Basic and above | Broader passive analysis. |
adaptive | 5 | Pro and above | Adds checks when the initial result needs more context. |
deep | 5 | Pro and above | Comprehensive analysis without catch-all probing. |
catch_all | 20 | Enterprise or entitled accounts | Deep analysis with catch-all probing. |
Company Validity Beta is an explicit paid-plan opt-in and currently adds no credits beyond the selected profile. Profile access is enforced by the API.
disposable_only, strict_disposable, guess, or run_catch_all. New integrations should select a named profile instead.Quota behavior.
Free usage is counted in a UTC calendar-month window. Paid usage is counted within the current Stripe subscription period. For an active paid workspace, the effective limit is the plan's included credits plus active additional credits granted for that same period.
The billing and usage views report included credits, purchased credits, the effective
limit, usage, remaining credits, and the current period boundaries. If a request would
exceed the effective limit, the API returns 429 with a structured
monthly_credit_limit_exceeded response. Rate
limits are enforced by the API and front-door server controls.