Every AI decision
deserves a receipt.
Ink Receipts is an open developer platform for issuing portable, cryptographically verifiable receipts for AI decisions.
Built on the BIL Kernel, every receipt captures exactly what happened, when it happened, why it happened, and how it can be verified.
Issue once · Verify anywhere.
Traditional logs tell you what a system claims happened. Ink Receipts produce evidence that can be independently verified — for banking, insurance, healthcare, legal proceedings, compliance, and regulated enterprise software. Edit the record below and watch the kernel produce one in front of you.
Decision Record
Pipeline
record → canonical → hash → receipt → bundle → verifyTamper Test
flip one field after sealing → verifier flips to FAILWhat is an Ink Receipt?
A portable evidence artifact for a single decision.
Instead of asking “Can we trust this output?” you can ask “Can we reconstruct exactly how this output was produced?”
Each receipt is designed to move between organizations — a bank can issue it, an insurer can verify it, an auditor can inspect it, a regulator can replay it, a court can evaluate it — with no access to the original system.
Each receipt can include
- request
- response
- model identity
- prompt hash
- policy references
- timestamps
- signatures
- evidence chain
- verification metadata
Why developers like it
Milliseconds
Issue receipts in milliseconds.
Anywhere
Verify them anywhere.
Any store
Store them anywhere.
No chain
No blockchain. No centralized trust.
let receipt = ink.issue(decision)?; receipt.verify()?; receipt.export_json()?; receipt.sign()?;
Built on the BIL Kernel
An open runtime for institutional evidence.
The BIL Kernel is the open-source runtime that powers Ink Receipts. It provides a minimal, deterministic evidence layer for institutional software — so developers build on one common substrate instead of inventing a new receipt format for every application.
The result is portable evidence rather than application-specific logs.
BIL Kernel on GitHub ▸Core primitives
- Identity
- Time
- Event
- Value
- Obligation
- Evidence
- State
Beyond logging
Logs are operational.
They answer: Did the service run?
Receipts are evidentiary.
They answer: Can an independent third party verify the decision?
Ecosystem
Applications
│
Banking · Insurance · Legal · AI
│
Ink Receipts SDK
│
BIL Kernel (OSS)
│
Identity · Time · Event · EvidenceThree layers, one substrate.
- BIL KernelOpen-source infrastructure. The neutral, reusable foundation.
- Ink ReceiptsDeveloper platform — SDKs, CLI, APIs, hosted verification, integrations.
- BankabilEnterprise decision infrastructure for regulated institutions.