Billing & Plans

ShieldLabs bills per request, not per monthly active user. One identification is one request. You pick a plan that covers the request volume you expect, and that plan covers everything ShieldLabs does with each request: the Risk Score, the anonymity signals behind it, the persistent identifiers, and the patterns computed over time. Manage your plan and payment method under Settings in the dashboard.

​

What counts as a request

​

Plans

The Free plan is a one-time allowance of 5,000 identifications. Starter, Growth, and Scale each give you a monthly request balance, and the per-1,000 rate above is the effective price within each tier. For traffic above the Scale tier, Custom volume is a committed-volume quote — contact us.

​

Billing frequency

Pick monthly, quarterly, or yearly. Longer commitments cost less per request: Change your plan or billing frequency any time under Settings → Plans & Requests in the dashboard.

​

What every plan includes

Every plan — Free, Starter, Growth, and Scale — ships the full feature set. The tiers differ on monthly volume, how many domains you can keep active, and the per-domain ingest rate on the gateway. Scale adds priority support on top.

• Identification — a persistent VisitorID and DeviceID for every visitor.
• Anonymity signals — VPN, proxy, Tor, Privacy Relay, anti-detect, and the rest.
• Risk scoring — the explainable 0–100 Risk Score with its signals.
• Patterns — ready-made relationship patterns over your historical data.
• Risk analytics — the real-time dashboard, every breakdown, and CSV / JSON export.
• API — read scored results from your backend.
• Webhooks — scores pushed to your endpoints in real time.
• Support — included on every plan; Scale adds priority support.

​

Compare all features

All paid tiers ship the same capabilities; the plans differ on volume, active domains, ingest rate, and retention. Identifications Identification Anonymity Signals Automation & Headless Risk Scoring Abuse Patterns Analytics API & Delivery Platform & Support

​

Estimating your monthly requests

Your request usage is driven by how often you identify visitors:

​

When you run out of requests

If your request balance is exhausted, you get HTTP 402 (out of requests) when the snippet posts an identification to be scored. History and profile reads do not return 402. The fix is to upgrade your plan or add to your request balance.

​

Next steps

Compare features and pick a plan under Settings in the dashboard. To wire the score into your own decisions, read Acting on the Risk Score and the webhooks setup. The Server API and the API overview document programmatic reads and the exact endpoints that do and do not bill.