/ 01
Generate
Create a dedicated Ed25519 key pair for each agent. Private keys are generated locally and stay under your control.
Private previewBuilt on the emerging Web Bot Auth standard
A passport for
every agent.
Give your AI agent a portable cryptographic identity. AgentProof helps you create keys, publish them correctly, and prove which agent is behind every signed request.
WEB BOT AUTHED25519RFC 9421PORTABLE IDENTITYCLIENT-SIDE KEYSREQUEST SIGNATURESWEB BOT AUTHED25519RFC 9421PORTABLE IDENTITYCLIENT-SIDE KEYSREQUEST SIGNATURES
The protocol, simplified
Identity in three moves.
AgentProof packages open cryptographic standards into a workflow that takes minutes—not a security engineering sprint.
/ 02
Publish
Expose the public key at a stable HTTPS identity URL in the Web Bot Auth directory format.
/ 03
Prove
Sign outbound HTTP requests so compatible websites and infrastructure can verify which agent sent them.
Live identity lab
Don't take our word for it.
Generate a real Ed25519 key pair and verify a signature in your browser. Nothing leaves this page.
identity-lab / browser session
keys stay on this device
Identity details
Name the agent.
We'll make the keys.
Your identity will appear here
AgentProof uses your browser's Web Crypto API. No private key material is transmitted or stored.
Experimental demo · keys are not persisted or registered with third-party verifiers
From key to control plane
The boring identity work, handled.
Important distinction
A valid signature proves identity—not intent, reputation, or permission. Websites always retain control over what an agent may access.
Portable by design
Use an identity you can move to your own domain. Your agent should not be trapped behind ours.
Keys you control
Generate in-browser today, then connect your own KMS as your agent moves into production.
Lifecycle, handled
Rotate, revoke, expire, and monitor agent keys from one operational control plane.
Compatibility checks
Catch malformed directories and signatures before a CDN or website rejects your traffic.
Why now
The web can't run on “trust me, I'm an agent.”
Cloudflare, AWS, Akamai, Vercel, Google, and other infrastructure providers are adopting cryptographic bot identity. The standard is emerging; the developer experience is not.
Request check
Identity directory found
Public key resolved
Request signature valid
Cryptographic identityVERIFIED
We're building in public
Your agent already has a name.
Give it proof.
Try the identity lab, break it, and tell us what your production agent would need next.
Generate an identity