SDK Demo
Try not.bot Verify: Request information from a human and review the response.
This page is a thin wrapper around the not.bot™ Verify Web SDK. Choose what to ask for, write the message the signer will see, respond in the not.bot app, and view the response data not.bot Verify receives.
Live demo. No personal data is stored, except for alias identifiers (DIDs) and site passes.
Step 1Permalink to Step 1
Build the request.
Step 2Permalink to Step 2
Respond in the app
Scan with your phone’s camera.
Opens the app on this device.
Why that address is not a link
The button above opens the same request through notbot://. Tap an https://not.bot link from a page already on not.bot and the phone keeps you in the browser: iOS and Android both read it as navigation inside this site and skip the hand-off to the app.
That applies to not.bot’s own pages. Your site should use the https:// address. It opens the app for anyone who has it, and shows the rest what to install.
Request data
The request this page sent to the signature server, as sent. requested_message travels as UTF-8 bytes and expires as Unix seconds; both are shown decoded.
Step 3Permalink to Step 3
Response data
Claims
Signature metadata
Response payload
The VerifySignatureResponse as returned, with the presentation bytes shown base64-encoded for legibility.
None of this personal data has been stored, except the alias identifier (DID) and the Site Pass. The claims above live in this page and in the demo server’s memory, which drops them thirty minutes after the request; they are never written to disk.
Why not.bot VerifyPermalink to Why not.bot Verify
What just happened, and what it costs you.
- not.bot Verify runs in your infrastructure, not ours — this request was answered by a deployment, not by a service we operate on your behalf.
- Julia Social is not contacted when a user answers a request. True of a deployment running in your infrastructure. This instance of not.bot Verify is running at Julia Social.
- You are billed per monthly active user — one unique not.bot alias interacting with your deployment in a month. The same person answering ten requests is one MAU, not ten.
- You can confirm someone is over 18 without learning their birth date, their age, or their name. A threshold answers yes or no.
- A Site Pass brings the same person back as the same pseudonym on your site, and is useless to every other site. Recognition without an account.
- Only a human with a verified not.bot alias can produce a signature like the one above.
Want this on your own site?