Answers before your first bank diligence.
The questions AI founders and developers ask us before shipping a bundle.
What is a BLKBXS receipt?
A signed, hash-chained record of one consequential AI action. It binds model, version, input/output hashes, policy reference, control results, human review, signer, timestamp, and verdict. It is verifiable without contacting BLKBXS.
What is an evidence bundle?
A bank-ready packet assembled from receipts. Eight sections: use-case summary, receipt map, model and version metadata, policy and control mapping, evidence digest summary, review packet sections, open diligence questions, and a reusable next-step checklist. See /examples.
Does BLKBXS see customer data?
No, not by default. The SDK is local-first and stores hashes and metadata. The receipt payload does not need to contain PII. If you want a hosted bundle, you choose what you upload.
What does the $2,500 pilot bundle include?
A one-time engagement that packages one AI workflow into a review-ready packet: use-case summary, receipt map, model and version metadata, policy and control mapping, evidence digest summary, reviewer-cut sections, open diligence questions, and a checklist for the next bank.
How is BLKBXS different from evals or observability?
Evals and observability produce signals — traces, scores, alerts. BLKBXS packages those signals into a portable evidence packet a bank reviewer can read. Your existing stack still runs. BLKBXS consumes its outputs.
Does BLKBXS make us compliant?
No. BLKBXS helps create, preserve, and present evidence for review workflows. It does not make a company or a bank compliant by itself. Model risk, vendor risk, legal, and audit still own their reviews.
Can we use our existing traces and evals?
Yes. Receipts can bind trace IDs, eval commitments, policy checks, and approval records from the tools you already run. BLKBXS is a packaging layer, not a replacement stack.
Is the terminal demo live?
The /terminal page is a scripted preview today. The live interactive SDK is launching at sdk.blkbxs.xyz — join the waitlist to run it against your own project.
What happens after the first bundle?
You keep the receipts, the bundle, and the signing keys. The next bank's diligence reuses the packet with a fresh cut. Recurring packet generation moves to the Evidence API Starter ($499/month) when that cadence justifies it.
What's the connection to Bankabil and INK Receipts?
INK Receipts is the open proof primitive. BLKBXS is the developer product that turns receipts into bank-diligence bundles. Bankabil is the institutional evidence layer above both.