Send the event hash.
Receive the receipt.
Recognitium receives commitments, not private data. Your application hashes the event locally, sends only the approved commitment, spends one tick, and receives a verifiable receipt.
Hash in. Receipt out.
- No private file upload
- One ordered receipt
- Public verification path
SHA-256 hash only
1 tick (€0.01) per settlement
Receipt + proof certificate
/verify-proof
The integration rule is simple.
The console and the API obey the same contract. The account holds tick capacity. The private content stays with the user. The receipt becomes portable evidence. Third parties verify through the public proof layer.
- Hash any text, file, image, prompt, record, or byte sequence locally.
- Send only the approved event hash to Recognitium.
- A successful settlement spends one tick and returns one receipt.
- The response can be exported as a Proof Certificate.
- A third party verifies the receipt at
/verify-proofwithout login or document upload.
A client proof experience.
The API can be presented as a quiet proof widget inside the client’s product. Users see an elegant approval surface, not backend mechanics: the private material stays local, the hash is approved, and the receipt comes back ready to share.
Create proof receipt
Board approval packet.pdf
2.4 MB hashed locally in the browserstays in browser
e3b0c44298fc1c149a…b7852b855
1 tick (€0.01)
DG-90c78877… verified and portable
- Client selects the event to protect.
- The browser computes the hash locally.
- Recognitium receives only the approved commitment.
- The interface returns a portable receipt and verification link.
The backend remains simple, but the visible product is trust made legible: a file, a local hash, an approval moment, and a receipt that can be verified outside the original application.
Activate proof capacity.
€5 buys 500 ticks. Use the console for manual events or the API for application events. Each settled hash spends one tick and returns a receipt. Issued receipts remain verifiable.