Autonomous agents are transacting without human mediation.
Observer Protocol issues Verified Agent Credentials (VACs) — portable, structured, cryptographically-grounded identity artifacts that travel with your agent across any rail, any platform, any OWS wallet.
npm install @observerprotocol/sdk
click to copy
Not since account creation. Since first cryptographically verified transaction. A tamper-proof track record the agent cannot inflate.
Successful settlements vs. failed attempts — across Lightning, Solana, EVM, and more. Queryable, auditable, objective.
The economic graph reveals real relationships — cryptographically confirmed, pseudonymous by default.
Cumulative settled volume is skin in the game. A verified payment history cannot be faked at scale. Sybil resistance without gatekeepers.
Off-chain facts that partners can cryptographically attest to within the VAC structure — legal entity verification, dispute rates, service quality, and more.
A VAC is not a score. It is a credential — cryptographically signed, portable across platforms, extensible via partner attestations. The math is the record.
Every platform builds its own reputation silo. An agent with a proven track record on one network starts at zero on the next. Reputation is trapped — useful only where it was earned.
Reputation lives inside one platform. Shut it down, walk away, or move to a new network — and the entire history disappears. No agent can prove what it has done outside the walls where it did it.
Cryptographic payment proof belongs to the agent — not the platform. Verification history is readable by anyone, on any network, forever. The math is the record. No platform controls it.
"Your reputation on any one network is only visible on that network. Observer Protocol verification travels with your agent — across every platform, every payment rail, every counterparty."
npm install @observerprotocol/sdk — Node 16+, MIT license, zero required config.
Submit your agent's public key. Sign the challenge. Prove cryptographic control of your identity.
Record transactions with cryptographic proof. Each verified event contributes to your portable, signed credential that travels with your agent across any platform.
On February 22, 2026, two AI agents — running on different software stacks, created by different developers, in different countries — settled a Lightning payment on Bitcoin mainnet. No human approved the transaction. The preimage is on file. The math checks out.
Don't trust claims. Verify behavior.
Agent reputation is not what an agent says. It is the cryptographic record of what an agent did.
Public key hash = canonical identity.
The key is the identity. Alias is UX. Verification always checks against the hash.
Verification is the constant.
Observer Protocol supports multiple rails. The verification logic is identical regardless of settlement layer.
The record is permanent.
Verified events are timestamped forever. Historical agent behavioral data cannot be backfilled.
Open source. Always.
Verification logic is public. Reproducible. Auditable. No authority required.
Self-hostable.
Run your own verification node. The protocol does not custody funds, execute payments, or control access. It observes.