Ship AI into banks with evidence bundles.
BLKBXS helps high-assurance AI startups turn receipts, traces, evals, policy checks, and review artifacts into bank-ready packets for vendor risk, model risk, security, compliance, audit, legal, and procurement.
Start free with the SDK. Generate your first receipt locally. When a bank asks for proof, ship a review-ready evidence bundle.
- model.id
- underwrite-agent-v2
- version
- 2.1.4 / cfg#7c9d
- loan.file.digest
- 0x4b21…e8a3
- input.hash
- 0x8f3a…c210
- output.hash
- 0x1d77…9e04
- policy.ref
- credit_policy_v3
- controls
- 4/4 fired ✓
- human.review
- required · approved
- signer
- ops-ceo-key-01
- verdict
- loan.approved
- prev.hash
- 0x77aa…01bd
When the bank asks for proof, BLKBXS helps you answer.
A regulated buyer does not only ask whether your AI works. They ask:
- What model version produced the action?
- What policy was binding?
- What evidence was used?
- What controls applied?
- What changed since the last review?
- Can this be verified later?
- Can legal, compliance, audit, procurement, and model-risk teams review it without rebuilding the story from scratch?
BLKBXS turns that scramble into a repeatable evidence packet.
Start free. Pay when the evidence needs to leave the building.
The first paid product is the $2,500 Bank Pilot Evidence Bundle — one AI workflow, packaged for one bank's diligence. The API and enterprise plane come later.
Free SDK
Generate signed receipts from your AI workflow locally. Bind model version, trace ID, policy reference, evidence digest, signer, timestamp, and review status. No customer data sent to BLKBXS by default.
Run a receipt locally →Bank Pilot Evidence Bundle
The first paid painkiller. Turn one AI workflow into a bank-ready packet for vendor risk, model risk, security, legal, audit, and procurement review. Ship in weeks, not quarters.
Build a bank pilot bundle →Evidence Bundle API
Repeatable evidence packets from receipts, traces, evals, policy checks, and control mappings — as your regulated customer pipeline grows.
See API plans →Enterprise Control Plane
SSO, retention policies, signing-key controls, audit logs, private deployment, partner exports, and governance-system integrations.
Discuss enterprise controls →Run the receipt before you read the memo.
Generate a receipt. Verify it. Tamper with it. Watch verification fail. Then generate a bank-review packet.
Open terminal demo$ blkbx receipt create --action loan.approved \
--model underwrite-agent-v2 --policy credit_policy_v3
receipt: 0x1d77…9e04 SIGNED ✓
$ blkbx receipt verify 0x1d77…9e04
VERDICT: VALID hash-chain intact
$ blkbx receipt tamper 0x1d77…9e04 --field verdict=loan.denied
$ blkbx receipt verify 0x1d77…9e04
VERDICT: INVALID signature does not match
$ blkbx bundle create --workflow underwriting --type vendor-risk
bundle: bnd_7c9d → 8 sections, 42 receipts, ready for review ✓Eight sections. One packet. Every reviewer.
AI use-case summary
Plain-language description of what the workflow does and where it acts.
Receipt map
Which actions produce receipts, with schema and coverage.
Model & version metadata
Model IDs, versions, configs, upstream providers.
Policy & control mapping
Bound policies, control checks, human-review gates.
Evidence digest summary
Signed digests, hash chain, verification results.
Review packet sections
Cuts pre-formatted for vendor risk, model risk, security, legal, procurement.
Open diligence questions
Known gaps and the answers we can and can't provide today.
Reusable next-step checklist
What to do when the next bank asks the same questions.
Founder
You are selling into a bank and diligence is the bottleneck.
Developer
You need a receipt in ten minutes and JSON, not a portal.
Solutions / sales-eng
You are answering the same DDQ for the fourth time this quarter.
Compliance / risk
You need defensible lineage across model versions and reviewers.
Your stack knows what happened. BLKBXS packages it for bank review.
Your team may already use tracing, evals, observability, guardrails, policy checks, or interpretability tools. BLKBXS does not replace them. It turns their outputs into portable evidence.
- Traces→ Receipts
- Evals→ Evidence commitments
- Policy checks→ Control mappings
- Approvals→ Review status
- Signatures→ Verifiable packets
Start free. Pay when the evidence needs to leave the building.
| Plan | Price | Use case |
|---|---|---|
| SDK Community | Free | Local receipts, CLI, sample schemas, CI examples |
| Bank Pilot Bundle | $2,500 one-time | One workflow packaged for bank review |
| Bundle Plus | $5,000 one-time | Custom workflow mapping and diligence prep |
| Evidence API Starter | $499 / month | Hosted packet generation, reviewer templates, share links |
| Enterprise Control Plane | Custom | SSO, retention, signing keys, audit logs, private deployment |
Reduce the time from diligence request to evidence packet sent.
< 10 min
SDK install → first receipt
< 30 min
First receipt → first evidence bundle
< 45 days
Bank pilot support
50%+
Evidence-prep time reduction
These are product goals and operating targets — not guaranteed regulatory outcomes. Every bank has its own review process.
Primitive
INK Receipts
The signed receipt as an open specification. Portable across stacks and vendors.
SDK & API
BLKBXS
The developer surface. Free SDK for receipts. Paid API for bank-ready bundles.
Institutional parent
Bankabil
The evidence-infrastructure doctrine for regulated finance.
Your model may be a black box. Your evidence cannot be.
BLKBXS gives AI startups a practical way to move from technical proof to bank-reviewable evidence.