Skip to main content
The @qed-proof/sdk package runs on Node.js 18 or later, Deno, and in browsers.

Install

Create a key

Sign in to the QED Proof app, open Developers → API keys, and create a workspace key. Keep the key private. In a server-side app, set QED_PROOF_API_KEY in the process environment; the client reads it automatically, or you can pass it when constructing QedProof. Do not put a workspace key in browser code. Browser applications can use the SDK’s local receipt verification, but send claims from a trusted server that keeps the API key private.

Submit a claim

Connect the destination first. This example checks a GitHub commit in a repository connected to your workspace:
The first response can be queued while QED Proof checks the destination. waitForVerdict polls until the claim is decided or the timeout expires. clientClaimId is an optional idempotency key: submitting the same ID again returns the same claim.

Verify a receipt

The SDK verifies receipts locally. Pass the raw JSON text when available so the integers-only check can distinguish a written integer from a decimal such as 1.0:
This checks the receipt’s schema, signature, digest, and Merkle inclusion without an API request for the receipt. The anchor is not checked unless you also provide an RPC URL. See the @qed-proof/sdk package or the HTTP API.