Four steps. No prerequisites. No glossary. You'll have a working receipt before we explain what's happening underneath.
When you finish step 4, you'll have a receipt that anyone — including someone with no H33 account — can independently verify. That's the win.
Pick a tier. Get an API key. Sandbox is free and good enough for the next three steps. Upgrade later if you need volume.
One HTTPS call. Your data in, a 74-byte cryptographic receipt out. The receipt itself is the artifact — keep it.
Hand the receipt to the verifier. The verifier doesn't need an H33 account. It doesn't need to call us. It works offline. The verifier returning VERIFIED is the win.
You just generated a cryptographic receipt that anyone can independently verify, anywhere, forever — even if H33 disappears tomorrow. Now we'll explain what that actually means ↓
You finished the artifact first. This is the part where the technology gets a name.
You generated a verifiable receipt. It contains a cryptographic commitment to your data plus three independent signatures. Anyone can recompute the commitment and check the signatures. If even one bit changes, the receipt fails verification.
Anyone can independently verify this result — your auditor, your customer, your insurer, a court — even if H33 disappears. The receipt outlives the platform that produced it. That's the difference between "we logged it" and "you can prove it."
Underneath: H33-74 (the receipt format), HATS (the continuous evidence layer), and three post-quantum signature families (ML-DSA, FALCON, SLH-DSA). One of those signature families being broken doesn't break the receipt. You don't need to know any of this to use it.
One thing. Wire receipts into the next system you'd like to be able to prove worked. An AI decision, a payment, a credential issuance, a data transformation. The receipt is the same shape for all of them.