Minimum-disclosure records
External pilot mode is hash_only. Decision records retain hashes rather than raw payloads, reducing unnecessary data retention.
Design-partner pilots now opening
Independent evidence infrastructure for AI systems.
When an AI workflow matters, application logs alone may not be enough. Judicore creates tamper-evident evidence records for consequential events so teams can verify what happened later without retaining the underlying sensitive payload in the decision record.
Hash-only pilot modeTenant-scoped keysChain verificationAPI-first
evidence_event.jsonVERIFIED
Consequential eventagent.action.completed
Evidence recordpayload_hash · record_hash
Chain anchorprev_chain_hash · chain_hash
INTEGRITY STATUSOK
✓
Application logs tell you what a system recorded.Judicore is built to make selected events independently verifiable.
Why Judicore
Evidence should survive the system that produced it.
Judicore sits outside the application or agent runtime. Selected events are recorded with cryptographic hashes and chained integrity data, creating a separate evidence layer that can be checked later.
Tamper-evident chain
Each accepted event returns record and chain hashes. Integrity verification checks the tenant chain for breaks.
Tenant-scoped access
Customer API keys are tenant-scoped with separated writer and auditor roles, plus controlled key rotation and revocation.
Replay-safe ingestion
Identical event replays are idempotent. A reused decision identifier with different content is rejected instead of silently overwriting history.
How it works
A narrow layer between an important action and a future audit.
Judicore complements your existing workflow, observability, and analytics stack rather than replacing it.
1
Select consequential events
Choose decisions or actions that would matter if someone asked what happened later.
2
Send the event
A tenant-scoped key authenticates ingestion. External pilot records retain hash evidence rather than the raw payload.
3
Receive chain evidence
The response returns a decision ID, record hash, previous-chain hash, and chain hash.
4
Verify later
Read back a decision, verify integrity, or export evidence when a review or audit requires it.
Production API
One bounded integration surface.
The first pilot focuses on ingest, readback, integrity verification, and evidence export.
POST /v1/ingest/decisionsGET /v1/decisions/{decision_id}GET /v1/integrity/verifyGET /v1/reports/decisions.csv
Built for consequential automation
Use Judicore where proving the event matters almost as much as executing it.
Evidence around high-impact calls, commitments, transfers, approvals, and agent actions.
Independent records for tool use, escalations, decisions, and automated actions.
Evidence for consequential operational or financial workflow events without replacing the system of record.
A separate integrity layer for stronger reconstruction and auditability around AI-assisted processes.
Design-partner program
Start with one workflow. Prove the evidence path. Then decide what deserves to scale.
We are opening bounded 14–30 day pilots for teams operating real AI workflows. The first pilot starts narrow, uses synthetic or otherwise low-risk data, and has explicit technical acceptance criteria.
Discuss a pilot01
Narrow scope
One workflow and a defined set of consequential events.
02
Synthetic first
Prove ingest, readback, idempotency, and integrity before bounded real traffic.
03
Explicit acceptance
Success requires integrity evidence—not merely a successful HTTP response.
04
Controlled credentials
Tenant keys are scoped, revocable, and transferred through an approved secure channel.
Judicore Partnerships
Need evidence that survives the workflow?
Request the one-page technical brief and sample integration.