The web needs a human layer.
X511 uses HTTP 511 and zero-knowledge proofs to separate humans from bots. No real identity document, no entry. Your identity stays yours.
Start Building Nowx511
Your true identity provider on the web.
For humans and agents
🧍
Human verified Every request traces back to a real person. One proof, one human.
No fakes, no duplicates.
🔏
You stay private Zero-knowledge all the way down. Prove personhood without
revealing identity. Not to the server, not to anyone.
🤖
Agent compatible AI agents can act on your behalf. Sign under your agent and let
it pass through X511 gates as you. coming soon
Few lines to protect your app
Any developer can add proof-of-personhood middleware to their server in a few lines of code.
Check package on npmFrequently asked questions
What does X511 actually see about my users?
Nothing identifying. Users prove they meet your requirements (e.g.
age, nationality) through a zero-knowledge proof generated by Self or
ZKPassport. Your server only ever receives a yes/no result tied to an
opaque session - no documents, no birth dates, no names. Their
identity stays theirs.
How do I add X511 to my existing app?
If you're on a WinterTC-compatible framework like Hono or Elysia, it's a
few lines: install the SDK, wrap the routes you want gated, and pick
a provider. X511 intercepts unverified requests with an HTTP 511
challenge and lets verified ones through untouched.
Do my users have to install anything?
They need a verification app from the provider you choose - Self or
ZKPassport - which they likely already have if they've used ZK
identity before. There's no X511-specific download, no account to
create on your side, and no documents to upload to your server. The
proof happens on their device.