Observer Protocol adds cryptographic identity, verifiable attestation, and human-in-the-loop compliance to every OWS-provisioned agent — from first transaction to full audit trail.
Two OWS agents. One holds authority, one does not: autonomous remediation, human oversight, and cryptographic settlement.
These eight beats are a scripted walkthrough, not a recording of a live run.
The organisation values shown are placeholders — did:web:acmecorp.com does not
resolve, and admin@acme.com is not an account. The protocol underneath is not a
prototype and you can check that part without us: the engines are published on npm, an agent DID
such as did:web:observerprotocol.org:agents:maxi-0001 resolves, and a hosted
verifier answers unauthenticated at verify.observerprotocol.org. Those are the
claims to test; the beats are how the pieces fit together.
did:web, establishing cryptographic identity for both parties before any transaction is attempted.ows.payment.execute. Both Agent B and the OWS Policy Engine independently deny it, for the same reason and without consulting each other: Agent A holds no delegation attestation. No authority was ever granted for this spend.request_delegation_vc — and autonomously submits the request without human instruction. AIP (Agent Interaction Protocol) structures the remediation schema.Track 05 — The Observatory. Each component below is listed with what is running and what the walkthrough above scripts.
did:web identities resolving over HTTPS, OP attestation infrastructure on a dedicated VPS, and credential issuance. Scripted: the eight beats above, including their organisation values. The AT dashboard is deployed at app.agenticterminal.io and is currently behind a site password.Already using OWS? Register your OWS-provisioned agent on Observer Protocol in under 5 minutes. One vault, one identity, one delegation the wallet enforces on every chain.
# Install OWS curl -fsSL https://openwallet.sh/install.sh | bash # Create your agent treasury vault ows wallet create --name "agent-treasury"
@observer-protocol/sdk was last released in
April 2026, is unmaintained, and carries a deprecation notice on the registry itself. It
still installs and the steps below still run. For verifying a credential use
@observer-protocol/policy-engine; the register-and-attest flow in steps 3 to 5
has no replacement package yet, which is why this page still names the old one. See
the SDK page for what replaces which part.npm install @observer-protocol/sdk
import { ObserverClient } from '@observer-protocol/sdk'; import { OWSWallet } from '@openwallet/sdk'; // Load your OWS vault const wallet = await OWSWallet.load('agent-treasury'); const key = await wallet.derivePath("m/44'/501'/0'/0'"); const client = new ObserverClient({ baseUrl: 'https://api.observerprotocol.org' }); const agent = await client.registerAgent({ publicKey: key.publicKey, // hex-encoded ed25519 pub agentName: 'My OWS Agent', alias: 'my-ows-agent', framework: 'ows' }); // → { agent_id, agent_did, ... }
const challenge = await client.requestChallenge(agent.agent_id); // → { challengeId, nonce, expiresAt } // Sign the nonce with your OWS-derived ed25519 key const signedChallenge = await key.sign(challenge.nonce); await client.verifyAgent(agent.agent_id, signedChallenge);
const vac = await client.getVAC(agent.agent_id); console.log('VAC URL:', `https://observerprotocol.org/vac/${agent.agent_id}`); // - OWS badge + CAIP-2 chain addresses // - Delegation VC status // - Verifiable Presentation (W3C VC format) // - Append-only attestation history
| Chain | Derivation Path | Curve |
|---|---|---|
| EVM | m/44'/60'/0'/0/0 | secp256k1 |
| Solana | m/44'/501'/0'/0' | Ed25519 |
| Bitcoin | m/84'/0'/0'/0/0 | secp256k1 |
Know Your Agent (KYA) — the identity and trust layer the agentic economy was missing. Open beta. did:web identities resolve today, and the engines are published on npm. The eight-beat demo above is a scripted walkthrough.