Docs · Getting started
For relying parties
Verify what an earner claims without ever seeing their raw statements. Five real steps, each linking to the actual page or route it happens on.
Step 1
Create an account and an organization
Sign up, then open the relying-party console and create an organization of kind relying_party. Keys, webhooks, and usage are scoped to whichever organization is active on your session.
Step 2
Get an API key
Console → API keys issues a real om_test_… (or, once verified, om_live_…) key — shown once, sent as Authorization: Bearer <key>. Every route the key can call is listed in the API reference.
Step 3
Verify a Proof
Three surfaces call the identical POST /v1/proofs/verify route, so they agree by construction: paste a presentation into Console → Verify; call the route directly from your own backend (see the API reference); or embed the @openmoney/verifier-sdk/widget custom element in your own page. An earner's share link opens the hosted verify page at a URL of the form /verify/{shareId} — the same verification, no integration required on your side.
Step 4
Request a Proof from an earner
Console → Request a Proof generates a real link an earner opens, signs in, and chooses which Proof to share back — calling POST /v1/proofs/requests. Set the policy it asks for under Console → Policies.
Step 5
Wire up webhooks and watch usage
Console → Webhooks delivers a real proof.verified event for every verification your API key performs. Console → Usage and Console → Audit log track real request volume and every mutating action on your organization.
No fabricated result
What verification checks
Verification fails closed on a bad signature, wrong audience, replayed or consumed nonce, revocation, or expiry — it never returns a valid result on any of those, and a missing credential shows an honest “unavailable” rather than an invented pass. The exact response shape (valid, claims, vct, issuer, warnings) is in the API reference under POST /v1/proofs/verify.