Live fingerprint demo

What a scanner sees when Capium drives the page

Below is a fingerprint report for a real Capium session: one coherent Windows 11 / Chrome device on a Richmond, VA exit. Every signal lines up, and the automation tells read clean. Next to it is the exact command we launched with.

The scan

https://fingerprint-scan.example/report

What we launched with

demo.py

from capium import launch_context

# License from CAPIUM_LICENSE_KEY or ~/.capium/license.
browser, ctx, page = launch_context(
    seed=48217,             # a coherent Windows device
    platform="windows",
    proxy="http://user:[email protected]:port",
    geoip=True,             # pin WebRTC IP + timezone + geo to the exit
    humanize=True,
    url="https://fingerprint-scan.example/report",
)

Resolved flags → scan values

--fingerprint=48217Master seed for the whole coherent device
--fingerprint-platform=windowsnavigator.platform, UA and UA-CH platform
--fingerprint-platform-version=15.0.0UA-CH platformVersion (Windows 11)
--fingerprint-windows-font-metricsDefault-text metrics match real Windows
--timezone=America/New_YorkIn-browser timezone (from geoip exit)
--fingerprint-location=37.5407,-77.4360Geolocation API coordinates (Richmond, VA)
--fingerprint-webrtc-ip=72.83.140.19WebRTC reports the exit IP, not your real one
--fingerprint-allow-3p-cookiesAllow third-party cookies for SSO / payment flows
--blink-settings=primaryPointerType=4,primaryHoverType=2Presents a desktop mouse, not a touch device

Why it passes: coherence, not disguise

A scanner does not just read values, it checks whether they agree. A Chrome User-Agent with the wrong UA-CH platform, a US exit with a European timezone, or a WebRTC IP that leaks the real host are the tells that get sessions flagged. Capium derives every surface from one seed, so the story holds end to end: UA Windows 15.0.0, a America/New_York clock, a Richmond exit, and a WebRTC IP pinned to that exit.

What we patch Start free