QuantZK Documentation

Verifiable Decision Infrastructure (VDI): cryptographic receipts any verifier can check offline.

Start here (billing wedge)

1. Quick Start: @quantzk/sdk authorize → record → verify
2. API billing pilot: authorize + attest + verify
3. QZR-1 receipt spec: portable .qzk Minimal / Standard / Strict
4. Charge authority: prior grant → charge continuity (not a gateway)
5. §4.4 freeze evidence: pinned committed-value registry + vectors
6. Charge Authority v1 freeze: claim-frozen artifact pins + reproduce
7. Charge Authority v1 reviewer map: claim → controls → tests
8. @quantzk/sdk: authorize() / record() → receipt → verify({ level })
9. Verify CLI: npx @quantzk/verify
10. LiteLLM adapter: usage callbacks → QuantZK receipts
11. API billing production: keys, migrations, Phase-2
12. Live demo: quantzk.com/vdi-billing
13. Browser verifier: /protocol/verify.html

What is QuantZK?

Open protocol for machine-checkable decisions. Issue a signed attestation; verify with math, not log exports. No QuantZK servers required for verification.

The billing wedge asks a simpler customer question: “Show me the QuantZK receipt.” Integrators call record / verify; they do not need Groth16 or VDI internals.

Who is this for?

• AI/ML Engineers: Prove your model followed fairness constraints without exposing weights
• Usage-billing / LLM platforms: Portable receipts for OpenMeter, LiteLLM, and finance disputes
• Compliance Teams: Cryptographic evidence that encoded policy checks passed
• Agent Developers: Trust between autonomous agents without shared state
• Platform Engineers: Verifiable decision audit trails
• Regulators: Independently verifiable proofs instead of self-reported logs

Core Concepts

Concept	What it does
QZR-1 receipt (.qzk)	Portable billing evidence envelope (Minimal / Standard / Strict)
Decision Attestation	A signed, portable proof that a decision followed rules
Verification	Offline checks: Groth16 ZK proofs + Ed25519 signatures + billing fingerprint
Phase-2 binding	In-circuit commitment binding required for QZR-1 Standard
Verification Receipt	A signed record that verification occurred
Verification Profile	Semantic agreement on what "verified" means
Transparency Log	Append-only log that detects verifier equivocation
Policy Manifest	A versioned, hashed set of constraints

Documentation

Guide	Description
Quick Start	SDK record + QZR-1 verify in minutes
API billing pilot	Local two-call HTTP runbook
@quantzk/sdk	Integrator SDK
Verify CLI	Offline npx @quantzk/verify
QZR-1	Portable receipt specification (Candidate)
§4.4 freeze evidence	Pinned committed-value registry + vectors
Charge authority	Prior grant → charge continuity (claims / non-claims)
Charge Authority v1 freeze	Claim-frozen pins + reproduce commands
Charge Authority v1 reviewer map	Claim → fields / controls / tests / non-claims
LiteLLM adapter	LLM gateway → receipts
Independent review prep	Auditor packet outline
API billing production	Production deploy, env, Phase-2
Core Concepts	Attestations, receipts, trust
API Reference	Full API for all packages
Trust Model	Receipts, TVS, profiles, transparency
Security Model	Threat model, circuit governance
FAQ	Common questions

Quick Links

• Protocol Specification (VDI-SPEC.md)
• Architecture Diagrams (ARCHITECTURE.md)
• Public verifier + QZR-1: ayitsomar/quantzk-verify (offline verifier, SDK, Verify CLI, conformance)
• Full monorepo (issuer API + SPA + protocol): ayitsomar/zkCaptcha-backend → protocol/
  Packages are not yet published as standalone public npm packages.

The Key Commitment

If QuantZK disappeared tomorrow, attestations issued with embedded verification keys would still verify with the open verifier and pinned artifacts, subject to profile, revocation, and artifact availability assumptions.

Verification keys are embedded in attestations. Verifier source is public at ayitsomar/quantzk-verify. The math doesn't change. This is infrastructure, not SaaS.

Offline QZR-1 Standard PASS with revocation NOT_CHECKED is bound billing evidence, not current governance clearance.