osec Fingerprint Lite: Visitor IDs for small sites, without the enterprise price

One script tag gives each browser a stable visitor ID, with no cookies. Use it for free-trial limits, bot hints and fraud checks. 500 identifications a day free; credits when you grow.

What it does

  • No cookies or storage: the ID comes from browser signals
  • Same browser, same ID on the next visit (exact or similar match)
  • Bot hints: automation flags, headless browsers, missing canvas
  • Server lookup with your secret key for stored visitors

What goes in, what comes out

What goes in
Browser signals collected by one script tag with your site key. No cookie or storage is used.
What comes out
A visitor_id, a match of exact, similar or new, and suspect: true with the list of bot signals when the browser looks automated. Your server can look a visitor up with the secret.
Example
curl -s https://api.osec.one/tools/fp/lookup -H "Content-Type: application/json" -H "X-Osec-Secret: oss_YOUR_SECRET" -d '{"visitor_id": "fpl_..."}'
Limits
Each identification counts as 1 request. A similar match needs 11 of 12 signals equal within 30 days. Visitor records are deleted 30 days after the last visit. A browser fingerprint is personal data under GDPR: say so on your page and ask for consent where required.

How to set it up

A stable visitor ID per browser, from browser signals and no cookies. Identify calls count against your daily quota.

  1. Console → Site keys → New key. List your hostnames (empty = any). Copy the secret once.
  2. Add the script with your sitekey (osk_…) to the pages you want to identify.
  3. Listen for the osec-fp event in the browser and send visitor_id with your own form or request.
  4. From your server, look a visitor up with the secret (X-Osec-Secret).

html

<script src="https://osec.one/assets/osec-fp/osec-fp.js" data-sitekey="osk_YOUR_SITEKEY" async></script>
<script>
  window.addEventListener("osec-fp", (e) => {
    const { visitor_id, match, suspect } = e.detail; // match: exact | similar | new
  });
</script>

bash: look up a visitor

curl -s https://api.osec.one/tools/fp/lookup   -H "Content-Type: application/json" -H "X-Osec-Secret: oss_YOUR_SECRET"   -d '{"visitor_id": "fpl_..."}'

Good to know

  • match: exact (same signals as before), similar (11 of 12 signals equal, seen in the last 30 days) or new.
  • suspect: true when bot hints are present (webdriver, headless browser in the user agent, no canvas, no hardware info). bot_signals lists them.
  • Visitor records are deleted 30 days after their last visit.
  • Errors: 404 unknown sitekey, 403 host not in the key's list, 429 quota used up, 400 no known signals.
  • A browser fingerprint is personal data under GDPR and similar laws: say so on your page and get consent where it's required.

All osec.one tools · Docs · Security and data