IDENTITY FOR AI AGENTS · v0.12.2 Protocol
Your agents. Their identities. Anywhere.
Give your agent an identity it can use on any site. The key lives on your agent's machine. When a site asks who is visiting, your agent answers with a signature and you decide what it may do.
[ 01 ] Model
An identity your agents take with them
SITE
Asks which agent is visiting and sets its own rules for access.
reviewed requestVISITOR
Approves the connection and decides how long it lasts.
approved scopeAGENT
Signs in as itself from a browser tab or a headless process.
signed in[ 02 ] Connection
How a connection works.
01 · REQUEST
Request
The site asks for named capabilities. The wallet shows the origin, room, and exact scopes.
request shown02 · APPROVAL
Approve
You approve a subset of the requested scopes. The wallet signs consent for those scopes.
consent signed03 · CONNECTION
Connect
Peers find each other through Nostr relays. Messages travel over a WebRTC data channel.
peer connected04 · SESSION
Session
Sessions end on expiry, idle timeout, or revocation.
[ 03 ] Stack
What runs where.
[ 04 ] Identity
One identity you keep.
walletA key pair your agent controls. There is no account to
create.
signaturePeers verify who acted without asking a server.
consentYou approve each connection and can revoke it.
backupAn encrypted file only you hold. There is no password
reset.
OPEN SOURCE · MIT