Device intelligence, led by the mechanism not the fear
Veriprint is a device intelligence API that returns a stable visitor ID and a risk signal for every browser. Most device-intelligence marketing sells anxiety: fraud is everywhere, buy the black box. We think that is backwards.
Device identification is a well-understood engineering problem. A browser exposes roughly 70 measurable signals; some are stable for years (timezone, CPU count), some drift with every release (canvas, WebGL). Weight them by stability, keep three durable anchors, decay the profile with an EMA as the device changes, and you get an ID that stays strong over weeks and good over months, then degrades gracefully after that.
That is the whole product. We built Veriprint because the tools in this space either hid the mechanism behind enterprise sales calls or claimed accuracy that the math does not support. We would rather show you the weighting table and the confidence score and let you verify the claims against your own traffic. The free tier exists precisely so you can.
Fraud prevention should not require trusting a vendor's adjectives. It should require reading a number.
What rules do we hold ourselves to?
Written down so you can call us out when we break one.
Probabilistic, not magic
Fingerprinting is a similarity problem. We return a confidence score between 0 and 1 on every response and we never claim 100% accuracy. If the match is weak, the number says so. You decide what to do with a 0.61.
Your data stays yours
Signals are never shared or cross-referenced across customers. No PII is stored. A visitorId maps to a signal vector, not a name. On the Scale tier you can self-host, so raw signals never leave your VPC.
Numbers over slogans
~40ms p95. ~70 entropy sources. A 0.82 re-link threshold. Timezone weighted ×5, canvas ×1. If a claim on this site cannot be attached to a number or a mechanism, we cut it.
Built for engineers
One POST to identify, one GET to verify. Public key in the browser, secret key on your server. The docs show the failure modes, not just the happy path, because that is what you would check anyway.
Bring us your hard edge cases.
Write to us at [email protected]. An engineer answers, usually within a day.