Sentriq developer docs
Sentriq is a fraud-intelligence platform: drop a lightweight browser SDK into your frontend, call a REST API from your backend, and get a deterministic, explainable risk decision back for every security event — signups, logins, password resets, and anything else you choose to report.
What Sentriq actually does
- Collects coarse, non-invasive browser signals (screen, hardware, platform, timezone, locale, storage capability, basic automation hints) — never canvas/WebGL/audio fingerprinting, never form input or credentials.
- Resolves a device server-side from those signals using a deterministic, weighted, explainable confidence score — not a statistical or ML model.
- Scores risk with a fixed set of deterministic, weighted signals (velocity, device/account relationships, automation heuristics, and more) and bands the result into a risk level.
- Maps that score to a decision —
allow,monitor,challenge, orblock— via customer-configurable thresholds. Sentriq returns the decision; your application enforces it.
What Sentriq deliberately does not do
We'd rather tell you up front than let you find out in production:
- No canvas/WebGL/audio fingerprinting.
- No ML-based risk scoring or bot classification — every signal is deterministic and rule-based.
- No VPN, proxy, Tor, or IP geolocation detection today. The data model has fields reserved for this, but no provider is bound, so those fields are always
null. - No cross-browser or cross-device identity linkage, and no device merge/split.
- No CAPTCHA or challenge UI — Sentriq returns a decision, you decide how to act on it.
- No compliance certifications (e.g. SOC 2, ISO 27001) are claimed.
Where to start
- Quickstart — install the SDK and get your first risk decision.
- Browser SDK — full client-side API reference.
- REST API — server-to-server endpoints for devices, events, and risk assessments.
- Device resolution and Risk & decisions — how the two core engines work.