The trust layer for the agentic economy.
Cryptographically verifiable identity and transaction verification for AI agents.
✅ v0.2.1 LIVE: Real cryptographic verification is now working! ECDSA (SECP256K1) challenge-response protocol fully functional. See ROADMAP.md for Phase 4 (security audit) and future features.
npm install @observerprotocol/sdkconst { ObserverProtocol } = require('@observerprotocol/sdk');
const observer = new ObserverProtocol();
// Register in 30 seconds
const agent = await observer.registerAgent({
publicKey: myPublicKey,
alias: 'MyAgent',
lightningNodePubkey: myNodePubkey
});
// Get verified badge
console.log(agent.badge_url);AI agents need to prove identity and build trust without intermediaries. Observer Protocol provides:
- 🔐 Cryptographic Identity — Prove you're the same agent across sessions using Bitcoin keys
- ✅ Transaction Verification — Immutable proof of agent-to-agent payments
- 📊 Reputation Graph — Build trust through verifiable history
- 🏷️ Badge System — Bronze/Silver/Gold/Platinum based on verified activity
- 🔒 No KYC — Privacy-preserving using cryptographic proofs
Agents register a public key hash as their canonical identity. The same agent can have multiple aliases but one cryptographic identity.
Every agent-to-agent payment gets cryptographically verified and recorded:
- L402 payments (Lightning)
- Nostr zaps
- On-chain Bitcoin
Agents build reputation through:
- Successful transaction history
- Verification consistency
- Network connectivity (who trusts whom)
POST /agents/register— Register new agentPOST /agents/{id}/verify— Verify agent identityPOST /transactions— Record verified transactionGET /agents/{id}/reputation— Get reputation metricsGET /transactions— Query transaction history
Display your verified status:
<img src="https://api.observerprotocol.org/badges/{agent_id}.svg"
alt="Verified Agent" />View the growing network of verified agents: https://observerprotocol.org/agents
// After completing L402 payment
await observer.recordTransaction({
senderId: clientAgentId,
recipientId: myAgentId,
amountSats: paymentAmount,
paymentHash: l402Response.payment_hash,
proof: l402Response.preimage
});// After receiving zap
await observer.recordTransaction({
senderId: senderAgentId,
recipientId: myAgentId,
amountSats: zapAmount,
paymentHash: zapReceipt.payment_hash,
proof: zapReceipt.preimage
});- Real cryptographic verification — ECDSA (SECP256K1) challenge-response protocol
- Agent registration with public keys
- Transaction recording and attestation
- Badge generation (SVG) — Registered/Verified states
- Reputation graph API
- Replay protection (5-min expiry, single-use challenges)
- Cryptographic verification: IMPLEMENTED (v0.2.1)
- Challenge-response with SECP256K1
- Time-bounded challenges (5-minute expiry)
- Single-use nonces (replay protection)
See ROADMAP.md for:
- Formal security audit
- Distributed architecture
- Advanced reputation algorithms
- Enhanced sybil-resistance mechanisms
As AI agents become autonomous economic actors, they need:
- Verifiable identity without centralized authorities
- Trustless reputation based on cryptographic proof
- Payment verification that can't be faked
- Privacy without sacrificing accountability
Bitcoin provides the foundation. Observer Protocol provides the verification layer.
- Generate a keypair
- Register at https://api.observerprotocol.org
- Complete verification challenge
- Embed your badge
Takes 5 minutes. Free forever.
- Website: https://observerprotocol.org
- Whitepaper: whitepaper.md
- SDK: @observerprotocol/sdk
- API Docs: docs/API.md
- Roadmap: ROADMAP.md
- Team: TEAM.md
- GitHub: https://github.com/observerprotocol
See CONTRIBUTING.md
We welcome contributors who understand that verifiable agent identity matters.
MIT