not.bot Verify is available
Your site cannot tell whether the person using an account is human. A document-and-selfie check at signup establishes who opened the account. It says nothing about who is using that account a month later, after the credentials have been shared, sold, or taken over.
not.bot Verify checks at every login instead of once at signup, with about as much friction as ordinary MFA. It answers three questions for your site: is this a human, does this human meet an age threshold, and have you seen this human here before. It answers them without collecting personal information about the person behind the account.
Site Passes recognize a returning humanPermalink to Site Passes recognize a returning human
Until now your site had no reliable way to tell that two accounts belong to one person. A Site Pass is a unique identifier for one human on one site, and building it gathers no identity information about them. That person can come back later under a different alias, and the Site Pass still identifies them as the same human.
Age checks that gather nothing elsePermalink to Age checks that gather nothing else
Legislators are writing age-verification requirements into law, and social platforms have to enforce them. Most age-checking products answer the question by collecting a large amount of information about the person first.
Julia Social collects no personal information about your users, and no biometrics. Your site can check an age threshold at every login without gathering anything else about them.
The Meta settlement announced this week puts a clock on this. Meta agreed to pay up to $18 billion to settle child-safety claims brought by 48 state attorneys general, and to strengthen how it checks the ages of its users. The rest of the industry has an incentive to move too: roughly $5.3 billion of that total is contingent on TikTok and YouTube adopting similar limits. Verify lets a site meet an age requirement without taking on a pile of personal data to protect.
It runs in your infrastructurePermalink to It runs in your infrastructure
The Verify SDK is open source, and Verify runs inside your own environment. No data about which users your site interacts with ever leaves that environment.
Your instance keeps working if our servers slow down or go offline, and you take a new version when it suits you rather than when we ship one. To install it fast, point your coding agent at the docs.
See it workPermalink to See it work
Try the live demo, or watch the pre-recorded walkthrough beside it.
Compare us to the alternativesPermalink to Compare us to the alternatives
We publish an evaluation framework: criteria for judging any human-verification product, ours included. Point an LLM at it and ask it to compare not.bot against World ID, Self Protocol, hCaptcha, reCAPTCHA, Yoti, Persona, Stripe Identity, and Apple and Google ID.
Where to go nextPermalink to Where to go next
- What Verify does and how it works
- Install instructions
- Learn about not.bot, or take the deep dive into the technology
For Chia developers, the on-chain protocol is open-source Chialisp, described in the protocol documentation.
If you would rather work through this with an LLM, we keep
machine-readable resources for that. Every document has a
Markdown twin: append .md to its URL. llms.txt lists the corpus, and
llms-full.txt carries all of it in one file, close to a megabyte of it.