Runnable receipts
Do not take our word.
Run it yourself.
Three Hive typed receipts have live example windows. You press a button, your browser posts a real request body to the real verifier, and you read the answer it sends back. Passing cases and failing cases both, because a proof system that only shows you its wins is a brochure.
These pages are written for card networks, payment processors, banks, exchanges, custodians, transfer agents, security teams, and compliance teams. Each one opens by naming the problem the receipt solves for you, in plain words, before any code appears.
The three live windows
Ten example cases.
Six of them fail on purpose.
Every example below is a real request body that has been run against a live verifier. Base URL for all three is https://thehiveryiq.com/v1. Verify routes are open and need no credentials.
Ledger Parity Receipt
Two systems hold the same book and one of them drifts. Prove what both sides looked like at the same moment without either side disclosing a position or a balance.
Knowledge Timestamp Receipt
A disclosure clock starts when the machine knew, not when a person read the alert. Pin the machine's moment while it is still true.
Screening Attestation Receipt
You screened a counterparty. Later you have to prove which list version you used and who signed off on the answer.
Read this before you trust anything below
These example receipts are signed with published demonstration keys. Their key ids all start with did:hive:example: and their seeds are public. Nothing here is secret.
Anyone can regenerate them. That is the point. It shows the API is doing real signature and gate work on the bytes you send, not handing back a canned answer.
Because the seeds are public, an example receipt is a demonstration and it is never evidence of a real event. The response says so itself, in the field key_trust: example_registry. Read that field on every result below.
How to read a result
Four fields tell you everything.
The fields that matter
valid is the verdict. failed_gate names the specific check that rejected the receipt, and it only appears when something failed. reason says it in words. key_trust tells you how much the signing key is worth, and on every example here it reads example_registry, which means demonstration only.
A failing case is a working system
Six of the ten cases fail. That is the interesting half. A gate that never rejects anything is not a gate, and a verifier that returns valid true for whatever you send it is not verifying. Watch which gate catches each bad receipt and why.