Every other tool detects bots — a probabilistic guess that sophisticated fraud slips past. 5arz does the opposite: it issues affirmative, cryptographic proof that a real, attentive human was there — a signed credential per impression or action, verifiable by anyone.
Talk to us → See the APIThe problem is no longer at the edges — it's the majority of traffic.
There are three approaches to "is this a human?" Only one hands you portable, signed proof.
| Detection (DoubleVerify, IAS, HUMAN) | Orb personhood (World / iris) | 5arz | |
|---|---|---|---|
| What it produces | A probabilistic score / blocklist | A unique-human ID | A signed proof a real human did a specific action |
| Affirmative proof? | No — it's a filter | Personhood only | Yes — a credential per impression/action |
| Hardware / biometric custody | Page-level | Orb + central enrollment | None — phone; biometrics stay on-device |
| Verifiable by anyone | No (closed) | Limited | Yes — public JWKS, any JWT library |
| Legal status of the output | None | None | Ownable property (UCC Art. 12) |
Detection tells you it probably wasn't a bot.
5arz hands you a signed receipt that a real human was there — that you can verify, and own.
An ES256-signed credential (Proof-of-Human-Fulfillment) attached to a verified human impression or action — tamper-evident, timestamped.
Anyone downstream validates it against our public JWKS with any standard JWT library — no 5arz SDK, no lock-in.
Verified human output is a Controllable Electronic Record — clean, take-free chain of title to the human signal in a bot-poisoned market.
Pay for humans, prove you got them — per-impression receipts, not after-the-fact estimates.
Offer "verified human" inventory backed by signed proof, not a probabilistic label.
You sell the promise — 5arz is the cryptographic verification route you can plug in today.
Buy training data and attention with proof a real human produced it.
One API call per impression or action you want proven.
5arz confirms a real, live human on-device — privacy-preserving.
A signed Proof-of-Human credential is issued for that event.
Validate against the public JWKS — downstream, no SDK.
Bring us your traffic, your inventory, or your verified-human product — we'll make every unit provable.
Start a pilot → Get an API key