Docs

Ageseal documentation

Add a wallet based age gate with one script tag and one server side check. Your visitor approves a single question in the wallet they already have, and your server receives a signed yes or no.

How it works

  1. Visitor browserRuns the SDK and the wallet picker. The wallet answers over 18, yes or no.
  2. AgesealStarts the session, verifies the wallet response in memory and signs the result.
  3. Your serverVerifies the token with Ageseal public keys and lets the visitor in.
  1. Your page calls Ageseal.check({ key, over: 18 }) when the visitor reaches the restricted action.
  2. The SDK asks Ageseal to start a session and passes the request to the browser, which opens its own wallet picker through the W3C Digital Credentials API.
  3. The visitor approves one question in their wallet: are they over 18. Nothing else is requested.
  4. Ageseal checks the issuer signature, the nonce and your origin, then discards the response and returns a signed token.
  5. Your page sends the token to your server. The server verifies the signature and the claims, and then lets the visitor in.

What you get

  • A small browser SDK loaded from a script tag, with no dependencies and no cookies.
  • A signed ES256 token that your server verifies offline with public keys, or optionally redeems once with your secret key.
  • A clear result for every attempt: pass, fail, or unavailable with a reason, so you can offer another check.
  • Test keys and a dashboard with counts per site. Failed and abandoned attempts are never billed.

What Ageseal keeps

Ageseal stores no personal data about the people whose age is checked. Only counts per customer account are kept.

Kept, per customer

  • Monthly counts of passed, failed and cancelled checks
  • The method used (mdoc, zero knowledge proof, OpenID4VP) and the age threshold
  • Your account, API keys and allowed origins

Never stored

  • The credential or anything inside it
  • Birth date, name, document number, photo, issuing country
  • Visitor IP address, browser fingerprint or cookies
  • Any identifier that links two checks of the same person

The details, including the token contents and the data flow, are on Privacy and security.

Where each part stands

Status of each part of Ageseal
PartStatusNotes
Browser SDKTest modeStarts a check through the API and asks the wallet. Live keys report unavailable until production issuers are added.
Script CDN and version pinningAvailableVersioned files with Subresource Integrity hashes.
Verification APITest modeAccepts test keys and test credentials only. The reference may still change before launch.
Token verificationTest modeES256 tokens and a public key set. Test tokens use their own issuer and audience.
Dashboard: sites, keys, domain verificationAvailableFor invited accounts. The waitlist is open.
Test mode and going liveTest modeTest mode is open to invited accounts. Going live needs production issuers and opens to the waitlist first.
WooCommerce and Shopify pluginsPlannedNo date yet.

Where to go next

  • Quickstart: add the script, call check, verify the token.
  • Browser SDK: options, results, reasons, browser support and version pinning.
  • Verify tokens: claims, public keys, key rotation and single use redemption.
  • HTTP API: endpoints, requests, responses and errors.
  • Fallback: visitors without a compatible wallet, and the never block rule.
  • Testing and going live: test keys, domain verification and a launch checklist.
  • Privacy and security: what is stored, what the token holds, and the standards used.