A cryptographically signed credential that a real, unique, attentive human did the work, the view, or the action — verifiable by anyone, no trust required. Detection guesses. 5arz signs.
Patents pending (US 63/979,052 + 63/979,474) · UCC Article 12 property class · Public JWKS · Live now
Proof of Human is affirmative, signed proof that a real, unique, attentive human performed a specific action — work, a view, a presence event, or a personhood check — issued as a portable credential anyone can verify against a public key, without trusting the issuer.
It is the opposite of detection. Detection is a probabilistic score that a system grades for itself and that sophisticated fraud slips past. Proof of Human is a real signature — checkable downstream by anyone, on any device, forever.
Every competitor covers one slice. None of them say all five.
A real ES256 credential anyone verifies via public JWKS — not a detection score that grades itself.
Real-time attention, liveness, and device attestation — not a one-time orb scan or a statistical guess.
One credential standard across all of them — not a single narrow check bolted onto a product.
Grounded in UCC Article 12 (Controllable Electronic Records) and patent-pending technology. No one else pairs proof-of-human with property.
Public JWKS, open SDK, in-browser verifier, reference on-chain contracts. Verify against our keys — we're infrastructure, not a walled garden.
Proof-of-Human is the category. 5arz wrote the definition, runs the standard, and issues the credential.
A verified person does the work, watches the view, or completes the check on their own device.
Real attention, liveness, and device signals are scored, then signed on the spot into a PoHF credential.
The signed token rides with the impression, the task delivery, or binds to a wallet on-chain.
Check the signature against the public JWKS with any JWT library — no 5arz SDK, no trust required.
| Capability | Bot detectionIAS · DoubleVerify · HUMAN | Orb / iris personhoodWorldcoin · Humanity | 5arz Proof of Human |
|---|---|---|---|
| Affirmative, signed proof (not a guess) | No — probabilistic | Partial | Yes — ES256 signed |
| Anyone can verify downstream | No | Closed | Yes — public JWKS |
| Proves a specific action happened | Inferred | No — just "a human exists" | Yes — bound to the action |
| No special hardware / central biometric DB | Yes | No — requires orb | Yes — on-device |
| Covers work + attention + presence + personhood | Attention only | Personhood only | All four |
| Legal property class behind it | No | No | UCC Article 12 + patents pending |
Category comparison by capability. Vendor names shown as representative examples of each approach.
Verified human impressions and attention — affirmative proof a real, attentive human saw the work, not a bot.
Provably human reasoning, preference, and judgment data — every datapoint signed by a verified unique human.
On-chain isVerifiedHuman(wallet) gating and anti-sybil — verified-human without exposing identity.
Prove a real human did the work an AI agent paid for — the fulfillment half of agent-to-human commerce.
Meter the credential: pay per Proof-of-Human verification. Self-serve key, free test mode.
Full API, SDK, JWKS, and on-chain reference. Integrate in minutes; verify anywhere.
Affirmative, cryptographic proof that a real, unique, attentive human — not a bot or undeclared AI agent — performed a specific action. 5arz issues it as a signed PoHF credential anyone can verify against a public key set, without trusting 5arz.
Detection is a probabilistic score that grades itself and that sophisticated bots slip past. Proof of human is a real signature asserting a human was present, checkable by anyone downstream. Detection guesses; proof is signed.
No special hardware and no central biometric database. Biometric data stays on the user's device; only a signed attestation leaves. And it proves a specific action happened — not only that a unique human exists somewhere.
Each credential is an ES256-signed JWT. Fetch the public keys from api.5arz.com/.well-known/jwks.json and verify with any JWT library — or paste it into the in-browser verifier.
Yes. A simple API issues a signed credential per action, settles over standard rails, and verifies downstream without a 5arz SDK. You distribute; 5arz is the proof layer. Read the docs →
Issue a signed proof instead. Free to start, verifiable by anyone.