Skip to main content
The qed command submits and lists claims, watches a claim for its verdict, fetches receipts, and verifies receipt files or HTTPS URLs.

​
Install

The CLI requires Node.js 18 or later:
Check that it is available:

​
Sign in

Create a workspace API key in the QED Proof app, under Developers → API keys. Then run:
The prompt hides the key as you type. You can also pipe a key through standard input with qed login --key-stdin. The CLI stores it in the operating system’s QED Proof config directory with owner-only file permissions. To remove it, run qed logout. QED_PROOF_API_KEY can be used instead of the saved key; QED_PROOF_BASE_URL points the CLI at a self-hosted node.

​
Submit and inspect claims

Connect the destination in your workspace before submitting. For a GitHub commit:
Use qed claims list --limit 20 to list recent claims, qed watch <claim-id> to poll a claim, and qed receipts get <receipt-id> to fetch a public receipt. Add --json to these commands for machine-readable output. The --id value is an optional idempotency key.

​
Verify a receipt

The CLI checks the receipt locally and exits with status 1 if it is invalid. It can also read an HTTPS URL, accept an alternate keys file or URL with --keys, and check an anchor against an RPC endpoint with --rpc:
See the Python SDK, TypeScript SDK, or MCP server for application and agent integrations. The @qed-proof/cli package includes the full command help.