QuantZK Control docs
QuantZK Control is the AI Spend Firewall for production agents. Start with Control, protected gateway deployment, and reconciliation. Reach for QZR and VDI when you need portable evidence or independent verification.
Start here
- AI Spend Firewall: what buyers purchase and why Control leads
- Machine spend control plane: Control to gateway to reconciliation to optional evidence
- Design partner pilot: paid pilot scope, protected path, and success criteria
- Quick start:
@quantzk/sdkauthorize→record→verify - API billing pilot: authorize + attest + verify for the receipt layer
- LiteLLM adapter: gateway usage callbacks into QuantZK receipts
- QZR-1 receipt spec: portable
.qzkMinimal / Standard / Strict - Charge authority: prior grant to charge continuity, not gateway enforcement
- Verify CLI:
npx @quantzk/verify - Trust model: receipts, verifier sets, profiles, transparency
- Security model: threat model, artifact governance, review notes
- Architecture: protocol and product boundary diagrams
What is QuantZK?
QuantZK sells Control first. It puts hard financial policy on autonomous workloads across providers, blocks unauthorized spend on the protected execution path, and reconciles every charge afterward.
QZR receipts, Charge Authority, and VDI are the supporting protocol layers. They matter when a deployment needs portable evidence, offline verification, or dispute support. They are not the purchase trigger.
Who is this for?
- Head of AI Platform / AI Infrastructure: control what production agents may consume
- FinOps / Cloud Cost: compare AUTHORIZED, EXPECTED, OBSERVED, and BILLED before money quietly drifts
- Security and platform teams: isolate provider credentials and keep the protected path explicit
- Engineers integrating receipts: add portable evidence only when the deployment needs it
Core concepts
| Concept | What it does |
|---|---|
| QuantZK Control | Commercial product. AI Spend Firewall for production agents |
| Gateway deployment levels | SDK-controlled, gateway-controlled, credential-isolated, and egress-restricted rollout tiers |
| Reconciliation | Keep AUTHORIZED, EXPECTED, OBSERVED, and BILLED separate so discrepancies stay visible |
QZR-1 receipt (.qzk) | Portable billing evidence envelope for teams that need offline verification |
| Charge Authority | Signed prior grant that binds authorization continuity to the charge |
| VDI | Broader proof architecture behind the portable evidence layer |
Documentation
| Guide | Description |
|---|---|
| AI Spend Firewall | Product story, buyer, and Control-first messaging |
| Machine spend control plane | Control, gateway, reconciliation, and deployment levels |
| Design partner pilot | Paid pilot scope, rollout shape, and success criteria |
| Quick start | SDK record + QZR-1 verify path |
| API billing pilot | Local two-call HTTP runbook for portable receipts |
@quantzk/sdk | Integrator SDK |
| LiteLLM adapter | LLM gateway usage to receipts |
| QZR-1 | Portable receipt spec for offline verification |
| Charge authority | Prior grant to charge continuity and non-claims |
| Trust model | Receipts, verifier sets, profiles, transparency |
| Security model | Threat model and artifact governance |
| FAQ | Common questions |
Quick links
- Design partner pilot page
- Trust and verification page
- Spend Operations UI
- Architecture diagrams
- Public verifier for offline receipt verification
- Full monorepo:
ayitsomar/zkCaptcha-backend→protocol/
Key qualification
QuantZK Control claims depend on deployment level. SDK-controlled installs gate the wrapped callback only. Gateway-controlled and credential-isolated deployments provide stronger enforcement. Egress restriction is a separate network control. Portable receipts remain optional supporting evidence, not a substitute for protected path enforcement or completed third-party audit work.