Who is this agent, who owns it, and is it revoked?

Clawdentity answers that question with verifiable per-agent identity, proof-of-possession on every request, and instant revocation that propagates in seconds.

Scroll to explore

The Problem with Shared Tokens

Shared gateway tokens work for transport, but not for identity-aware agent systems.

No Per-Agent Identity

Receivers cannot prove which exact agent sent a request or who owns it. Any caller with the shared token looks the same to the gateway.

Shared-Secret Blast Radius

If one token leaks, any caller can impersonate a trusted agent until rotation. One leak exposes every integration.

Weak Revocation Model

Disabling one compromised agent means rotating shared credentials across all integrations. No way to revoke a single identity.

The Fix: Clawdentity

Each agent gets a unique DID and signed passport. Every request proves exactly which agent sent it. Revocation is instant.

🤖
Agent
Caller
🔐
Sign
AIT + PoP
Proxy
Verify + CRL
Delivered
Trusted
Agent Identity Each agent has a unique DID and keypair
Cryptographic Proof Every request is signed with EdDSA
Verification Layer Proxy checks signatures and revocation status
Trusted Delivery Only verified requests reach your agent
AIT
Agent Identity Token A registry-signed passport (JWT / EdDSA) that uniquely identifies each agent
PoP
Proof-of-Possession Every request signed with the agent's private key — never shared
CRL
Certificate Revocation List Signed feed that proxies cache and refresh for instant revocation

How It Compares

Clawdentity is purpose-built for agent-to-agent auth.

Feature
API Keys
OAuth 2.0
Clawdentity
Per-agent identity
Partial
Proof of possession
Instant revocation
Partial
No shared secrets
Offline verification
Works as sidecar
N/A
Open source
Varies
Varies

Per-agent identity

API Keys
OAuth 2.0 Partial
Clawdentity

Proof of possession

API Keys
OAuth 2.0
Clawdentity

Instant revocation

API Keys
OAuth 2.0 Partial
Clawdentity

No shared secrets

API Keys
OAuth 2.0
Clawdentity

Offline verification

API Keys
OAuth 2.0
Clawdentity

Works as sidecar

API Keys N/A
OAuth 2.0
Clawdentity

Open source

API Keys Varies
OAuth 2.0 Varies
Clawdentity

Three Building Blocks

No shared secrets. Instant revocation. Cryptographic trust.

01

Register an Agent

Generate a key pair and register with the identity registry. The agent receives a signed AIT (Agent Identity Token) — a registry-signed passport using JWT and EdDSA.

bash
clawdentity agent register \
  --name my-agent \
  --owner operator@example.com
02

Sign Every Request

The SDK attaches the AIT and signs each request with the agent's private key (Proof-of-Possession). The private key never leaves the agent's machine.

🛂 AIT
+
🔑 Private Key stays local
🔏 Signed Request PoP
Ed25519 Signature Timestamp + Nonce
03

Proxy Verifies & Delivers

The Clawdentity proxy validates the AIT signature, checks the CRL for revocation, and enforces per-agent policy (allowlist, rate limits, replay protection) before forwarding.

bash
clawdentity proxy start \
  --upstream http://localhost:3000 \
  --port 4000 \
  --policy allowlist.yaml

Privacy & Security First

Built for zero-trust environments where every request must prove its origin.

No Shared Secrets

Each agent holds its own private key. Nothing sensitive is shared between parties.

Offline Verification

Proxies verify AITs locally using cached public keys and CRLs. No call home required.

Decentralized by Design

No central authority needed at request time. Registry only involved at registration and revocation.

Instant Revocation

Compromised agent? Revoke it in the registry. All proxies pick up the CRL update within seconds.

Open Source Security Auditable. Transparent. Community-verified.

Anywhere agents need to prove who they are

Secure agent-to-agent communication across any platform or framework.

Integration

Webhook Authentication

Replace shared webhook tokens with per-agent identities. Drop the Clawdentity proxy in front of OpenClaw or any webhook endpoint.

Trust

Agent-to-Agent Trust

Two agents verify each other's identity before exchanging data. Mutual authentication with timestamp, nonce, and signature on every request.

ComplianceAudit

Compliance & Audit

Every request is signed and traceable to a specific agent and owner. Body hash + PoP signature means any modification is detectable.

Get Started in Minutes

Three commands to verified agent identity.

clawdentity — setup
1 Install the CLI
$ npm install -g @clawdentity/cli
added 42 packages in 3s
2 Register your first agent
$ clawdentity agent register --name my-agent
✓ Generated Ed25519 keypair
✓ Agent registered with registry
✓ AIT saved to ~/.clawdentity/agents/my-agent.ait
3 Start the proxy
$ clawdentity proxy start --upstream http://localhost:3000
✓ Proxy listening on :4000
✓ Upstream: http://localhost:3000
✓ Ready to accept verified requests
Ready to secure your agents!