Quickstart

Three things people arrive wanting to do. Pick one.

1. Verify a credential someone gave you

From npm. No API key, no token, no Observer Protocol API in the path. It fetches the issuer's DID document and the revocation status list over ordinary HTTPS from the origins the credential names; point offline.didDocumentPath at a local copy and it makes no network call at all. The hosted verifier below is a different build of the engine, not this code path; where the two disagree the published package is authoritative.

npm install @observer-protocol/policy-engine
import { verifyCredentialObject } from '@observer-protocol/policy-engine'; const verdict = await verifyCredentialObject(mandate, config, Date.now());

Checks issuer, structure, validity window, the eddsa-jcs-2022 proof against the issuer's DID document, and revocation. Fails closed. Full details →

2. Integrate a rail

One adapter per rail. Each enforces a signed delegation at the signer boundary.

3. Read the specification

The Agentic Identity Protocol drafts and the delegation schemas.
github.com/observer-protocol/aip · delegation v2.7 · issuer DID document

The @observer-protocol/sdk and @observerprotocol/sdk packages are deprecated — use the adapters and the policy engine instead.

A hosted verifier is also open at verify.observerprotocol.org (POST /v1/verify, no token, rate limited), returning a signed verdict. Offline verification above remains the primary path: it needs nothing from us and cannot be revoked.

All documentation →