Axia Verify
Is it authentic? — for content, for live calls, for the human behind them.
Verification is free to ensure universal access to truth.
What it is
Axia Verify is the authenticity layer of the trust stack. It answers one question — Is it authentic? — across three modules: Receipt Verification for any signed file or page, Live Verification (Stream Guard) for cryptographically verifiable WebRTC calls, and Human Presence Verification (Biometric PAD L2+) so receipts can carry Verification Level 4.
How it works
Receipt Verification
Hash a file, page or asset and look it up via /verify/:hash or drop in <axia-verify>. Returns identity, key lifecycle, Merkle proof and Verification Level.
Live Verification (Stream Guard)
Capture any WebRTC stream, sign and Merkle-chain 2-second chunks. Receivers see LIVE VERIFIED — and VERIFICATION LOST the moment a chunk is replaced, replayed or injected.
Human Presence Verification (PAD)
Biometric Presentation Attack Detection at ISO/IEC 30107-3 L2 or higher proves a live human was physically present at enrollment, lifting receipts to Verification Level 4.
What you get
- Plain-language result: Verified by Axia / Unverified
- Origin identity (DNS-verified domain)
- Verification Level 1–4 (Identity + optional Human Presence)
- Merkle inclusion proof
- Embeddable <axia-verify> web component
- Embeddable <axia-stream-verify> live badge (Stream Guard)
- Offline-verifiable receipts (@axia/receipt-verify)
- Browser SDK: @axiaprotocol/stream-guard