Age Verify

What it does

AGE Verify is an identity verification service that uses passkey authentication combined with user-held encryption to enable anonymous age verification. During authentication, a cryptographic key is derived on the user's device and encrypts sensitive identity data before it reaches the server. This allows age verification results to be reused across different applications without exposing personal information.

The platform also offers proof of personhood verification, confirming that a human—not a bot—controls an account. Both services return only an anonymized result to the requesting application, not the underlying identity data.

Who it is for

Applications that need to verify user age or prevent bot accounts are the primary audience. This includes content platforms with age restrictions, AI services working to limit automated abuse, and any business requiring frictionless identity confirmation without collecting sensitive user data. The service targets both businesses implementing verification and end users who want to verify identity once and reuse that verification across multiple platforms.

Pricing

The site does not show prices.

How it stands out

The core differentiator is the encryption architecture. By using passkey-based authentication to derive an encryption key on the user's device, sensitive data never exists in unencrypted form on the company's servers. Even a full breach would expose only encrypted blobs, not readable personal information. Users verify once and then reuse the same proof across applications, reducing friction and repeated identity uploads.

The service explicitly positions itself as passkey-first, avoiding email-based authentication flows that introduce phishing vulnerability. The homepage emphasizes that only anonymized results are shared with applications—not names, birth dates, addresses, or ID images—giving users granular control over what information leaves their device.

What a founder should check

A competitor should investigate what happens when regulations require platforms to retain full identity records rather than anonymized proofs. Many jurisdictions have strict KYC and anti-money-laundering rules that may conflict with the user-held encryption model.

Second, verify adoption barriers. The service depends on passkey availability and user familiarity. If target customers still expect traditional ID upload flows, switching costs for integrating this new primitive could be high enough to limit market penetration.

Third, evaluate the moat around passkey-based encryption for identity. As the WebAuthn PRF extension becomes standard, the technical innovation may become replicable by larger identity providers. Understanding what prevents incumbents like Veriff or IDology from adopting similar architecture is essential.