QuantZK · Verifiable Decision Infrastructure
Verify every API charge.
QuantZK creates machine-checkable receipts for APIs, agents, and autonomous workflows, so customers can verify billing and policy checks without trusting internal logs.
Don't trust the logs. Verify the charge.
VDI protocol · api-billing-v2 pilot
Problem
Billing disputes still run on trust, not proof.
- Usage-based APIs and agents bill at scale; buyers only see invoices and vendor dashboards.
- Disputes become "trust our logs" vs "prove this line item."
- GRC and observability prove controls existed, not that this charge followed this policy at issuance.
Insight
Don't trust the logs.
Verify the charge.
Buyers want independent verification, not another export from the vendor's database.
Solution
VDI: machine-checkable receipts
VDI (Verifiable Decision Infrastructure) is an open protocol for portable decision attestations: Groth16 proofs, Ed25519 signatures, policy manifests. QuantZK is the product layer for issuance and verification.
Same bundle finance or a customer can re-run offline. No trust in your screen required.
Demo
See it fail when someone tampers.
1 · Billing demo
Step 1: attest + signed receipt. Step 2: independent verify. Edit one field → verification fails.
2 · Browser verifier
Verification runs entirely in your browser. Nothing is uploaded. Paste dashboard evidence JSON.
How it works
api-billing-v2 (pilot)
Meter event + tariff → deterministic charge → VDI attestation (ZK + policy manifest) → signed verification receipt Independent verify → Groth16 + Ed25519 + billing fingerprint match
- Signed meter envelope, tariff snapshot, replay guard.
- Self-contained JSON: verification key embedded; no call home after issuance.
- If QuantZK disappeared, issued receipts still verify.
Why now
The wedge is operational, not theoretical.
- Usage-based API pricing and agent workflows are exploding.
- Procurement and security ask for evidence buyers can verify themselves.
- Regulation pushes "prove the decision," not "we logged it" (EU AI Act, fair lending, HIPAA-style access).
- ZK + production verifiers are practical for per-charge proofs.
Roadmap
Wedge → expansion
| Phase | Focus |
|---|---|
| Wedge | Verifiable API billing (api-billing-v2, one endpoint pilot) |
| Next | Policy checks for agents and governed workflows |
| Protocol | Enterprise templates: lending, clinical, autonomous systems |
Business model
Infrastructure pricing
- Usage: per attest / per verify API call.
- Enterprise: dedicated issuer, SLAs, audit exports, key lifecycle.
- Pilot: 90-day single-endpoint program for usage-based billing.
Buyers: platform billing, FinOps, API product, security/procurement at usage-based SaaS.
Traction
Shipped in product today
Live
Billing demo, browser verifier, landing + docs
Protocol
VDI-SPEC, WHITEPAPER, conformance (JS / Go / Python)
CI
Billing pilot integration tests + runbooks
Security
NCC review track · BASL-aligned controls (site)
Next: [N] design partners · production issuer · $[Y] pilot ACV]
Team
Founder
Omar Roldan · Founder
Built QuantZK end-to-end as a solo founder: browser-local verification, deterministic billing attestations, replay-aware verification, adversarial integrity testing, and polyglot verifier runtimes (JS / Go / Python).
Focused on turning advanced verification primitives into deployable infrastructure for autonomous systems, not research-only protocols.
Ask
Raising $1M pre-seed
- Use of funds: issuer + verifier engineering, design partners, SDK/onboarding simplification, and production security review / cryptographic hardening.
- 12–18 months: launch verifiable billing pilots with API and AI infrastructure companies; harden issuer/verifier runtime for production; convert early design partners into recurring infrastructure revenue.