How it works
1
Open a session
Your server calls the API with an age requirement and a callback URL, and gets back an
opaque
session_id + nonce.2
Show the user a code
You render a QR code (or a tap-to-verify link) containing only
{ session_id, nonce }.
Your API key and callback URL never leave your server.3
The user approves in their wallet
They scan/tap and consent to share a yes/no. AnonAge computes the result server-side
from their already-verified age — never from anything the client sends.
4
You receive a signed result
AnonAge POSTs your callback URL with a signed
above_age_required boolean and a
receipt id. You verify the signature and unlock your content.What you get — and don’t
The result is always computed on AnonAge’s servers from a verified age claim. A client can’t
claim to be older than they are — closing the classic “trust the client’s age” hole.
Next steps
Quickstart
Integrate the full flow in about 10 minutes.
Authentication
Create and use API keys.
Callbacks
Verify the signed result (with copy-paste recipes).
API Reference
Every endpoint, request and response.