Comparison
LayerCall vs ShieldLabs
Both answer questions about whether a signup is real. ShieldLabs is a visitor identification service; LayerCall returns IP, email, phone, domain and device from one request. Which is the better buy depends on how many of those you need to ask about.
What each one is
Visitor identification aimed at unmasking traffic behind VPNs, proxies and anti-detect browsers, reporting device and network intelligence with a risk score.
Their current pricing →One request returns IP, email, phone, domain and device together, on one key and one quota — because the signal that catches a fake signup is usually the relationship between them, and that relationship does not exist inside any single check.
Our pricing →We never quote ShieldLabs’s prices. Where the table below states a fact about them, it is read from their own public page, linked beside the claim with the date we read it, and dropped if it goes sixty days unchecked. Their pricing is linked above and is always current.
About ShieldLabs’s side of this page: we describe what kind of product it is, and where we state a fact about it we quote their own public page, link to it, and show the date we read it — and we never quote their prices, which change without notice. Where their pages do not say, we say that rather than guess. Anything current comes from them: ShieldLabs’s own pricing page. Product names and trademarks belong to their owners; LayerCall is not affiliated with, endorsed by, or partnered with ShieldLabs.
Point by point
Every row is a point we set out to meet. Ours is checkable on this site; theirs is read from ShieldLabs’s own public pages, each claim linked to the page it came from and dated. A dash means their pages do not say — which is not a no.
| Point | LayerCall | ShieldLabs | ||
|---|---|---|---|---|
| Identifiers scored in one request | Yes | IP, email, phone, domain and device — one call, one key, one quota. | No | device, by category (visitor identification service). Not IP, email, phone and domain. |
| Cross-signal linkage | Yes | A device that reappears on a new email and IP is linked, and the link is in the score. | No | Not possible from a single-identifier check: there is no second signal to link device to. |
| A free tier that needs no card | Yes | 1,000 lookups a month, every endpoint, no card, no daily cap. At the limit it stops rather than billing. | Yes | Free is a one-time hard cap of 5,000 identifications, with no overage: further checks return 402 until a paid plan. their page → Checked 3 Sept 2026. |
| Device fingerprinting on every plan | Yes | Included on every plan, the free one too. | Yes | Device and browser fingerprinting with automation and headless detection; every plan ships the full detection stack. their page → Checked 3 Sept 2026. |
| The signals come back with the score | Yes | The signals behind it, and an allow / review / block verdict you tune with strictness. A number alone is unappealable. | Yes | Every risk score comes with the anonymity signals that shaped it and the weight each one contributed. their page → Checked 3 Sept 2026. |
| A test mode that never bills | Yes | Synthetic data, labelled as such in every response, never billed, never written to the shared network. How it works | No | Development and production are separate domains, and each domain gets its own keys and its own request balance. their page → Checked 3 Sept 2026. |
| Repeat lookups are not charged | Yes | Cached repeat lookups are free, every response carries billable_lookups, and you set your own spend cap. | Not stated | Overage can be turned off in dashboard Settings then Billing for a hard stop, after which further checks return 402. their page → Checked 3 Sept 2026. |
| Accuracy published with sample size and method | Yes | Published with the sample size, the method and the corpus. The figures | No | States up to 99% accuracy identifying visitors; no sample size or method published. their page → Checked 3 Sept 2026. |
| Verifies an AI agent's signature | Yes | Verifies an agent’s Web Bot Auth signature and decides what a verified agent may do. Agent endpoints | Not stated | Not stated on their public pages. Checked 3 Sept 2026. |
When ShieldLabs is the better buy
The problem is specifically multi-accounting and bonus abuse, where the question is whether two sessions are the same person behind different masks. That is an identity-resolution job, and a product built around it will go further on anti-detect browsers than a scorer that answers one signup at a time.
Weighing more than one option? Every ShieldLabs alternative we know of, ranked — including the ones that are a closer swap than we are.