Verify a CREB™ (Court Ready Evidence Bundle)
Submit a Report ID or CREB ID to verify authenticity, 14-of-20 SCN validator quorum signature, and JIL L1 anchor. Courts, regulators, and auditors can verify the seal independently - JIL's cooperation is not required, because the cryptographic anchor stands on its own. The sealed record itself is self-custody by the vendor. JIL stores hashes and locators only, never the plaintext blob.
Look up a Report ID
Enter the Report Identifier from the document's masthead (for example: JIL-VR-PS-2026-04-19-A8F3C2D1). The lookup returns verification metadata - it does NOT return subject PII. Retrieval of the sealed PDF itself requires vendor consent or a court order served on the vendor.
This record is authentic.
The record's issuer signature, validator quorum, and JIL L1 anchor have all been independently validated. This metadata is returned without subject PII; retrieving the sealed PDF requires vendor consent or a court order.
JIL staff: a higher-quota authenticated UI for live demos sits behind portal.jilsovereign.com/verify-record - sign in with your @jilsovereign.com Google account.
Try verification against a sample record
Each pillar ships a sample record. Verifying any of these returns a successful VERIFIED response with public metadata.
The mathematics of court-admissible evidence
A JIL Cryptographic Verdict Record is tamper-evident by construction. Verification does not require JIL's cooperation. Any party with a SHA-256 hash, an Ed25519 verifier, and public access to the JIL L1 ledger can validate the record end-to-end.
- Recompute the document hash.
sha256of the sealed PDF excluding the signature block. Must match the Content Hash in Section 0. - Verify the issuer signature. Ed25519 verify using JIL's published issuer public key. The signature covers the document hash.
- Verify the Sovereign Compliance Network (SCN) validator quorum. Each of the 14+ SCN validator signatures is Ed25519-verified against the SCN validator's published public key. Quorum threshold (70%) must be met across at least 10 jurisdictions.
- Verify the JIL L1 anchor. Look up the anchor transaction on the public JIL L1 ledger. The transaction must contain the verdict hash + Merkle root.
- Verify the 111-check Merkle root. Each per-check evidence hash in Section 4A rolls up into the root. Reconstruct the Merkle tree and match.
If any step fails, the record is invalid. The procedure is deterministic and reproducible - different verifiers will always reach the same result for the same document.
JSON verification API - available today
Forensic experts, regulators, and integrators building audit tooling can query JIL's public verification API directly. No authentication required. Responses include the same metadata shown above, in machine-readable JSON.
# Verify a single record by Report ID
curl https://jilsovereign.com/api/v1/verify/JIL-VR-PS-2026-04-19-A8F3C2D1
# Response (200 for verified records):
# {
# "status": "verified",
# "report_id": "JIL-VR-PS-2026-04-19-A8F3C2D1",
# "pillar": {"num": 1, "name": "Pre-Settlement Attestation", ...},
# "identifiers": {"attestation_id": "...", "vendor_id": "...", "profile_id": "..."},
# "verdict": {"disposition": "YES", "date_completed": "..."},
# "cryptographic_seal": {"content_hash_sha256": "...", "l1_anchor": {...}, "validator_quorum": {...}},
# "storage": {"sdv_posture": "vendor-controlled", "retention_minimum_years": 15, ...},
# "evidentiary": {"rules": ["FRE 702", "FRE 901"], ...}
# }
# Response (404 for unknown IDs): helpful "not_publicly_indexed" payload with
# four possible causes and the contact@jilsovereign.com contact pathway.
# List the manifest of all sample records
curl https://jilsovereign.com/api/v1/verdict-recordsThe endpoints set Access-Control-Allow-Origin: * so browser-based tools can query them directly. Cached 10 minutes on successful lookup, 1 minute on not-found. No PII ever returned.
Open-source verification tool
A standalone command-line reference verifier (jil-verify) is on the roadmap. It will reproduce the full verification procedure described above against a sealed PDF offline - validating the document hash, issuer signature, SCN validator quorum, JIL L1 anchor, and per-check Merkle root without any network dependency on JIL Sovereign. Target release: alongside the JIL L1 public client.
Until the CLI ships, the JSON API above provides the same verification data. For regulators and court-appointed experts who require a sealed, certified verifier binary signed by JIL Sovereign, contact contact@jilsovereign.com. SLA: 24 hours.
How non-vendor permissions actually work
Sealed CREB(TM) records are self-custody by the vendor who produced them. They live in that vendor's non-custodial Secure Document Vault (SDV). JIL is a verification layer, not a custodian: we hold cryptographic hashes, content-address locators, validator signatures, and L1 anchors - never the plaintext blob.
Every non-vendor party who needs access (auditor, counsel, regulator, court, executor, family-vault delegate, integrator) receives a vendor-issued grant. The vendor is the sole gatekeeper. Each grant is bound to a role and a constraint set:
- Role examples - auditor (read-only), regulator (subpoena-bound, audit-trailed), court (one-time bundle delivery), counsel (engaged-review, 30-day TTL), executor (posthumous, vendor-pre-arranged), owner-delegate (family-vault model). The vendor defines the role catalog; JIL enforces only the cryptographic protocol.
- Constraints per grant - explicit TTL, optional IP allowlist, watermarked retrieval, audit-log entry on every access, instant revocation by the vendor. The vendor sets the values; JIL signs and enforces.
- Verification stays public. Anyone with a Report ID can verify the seal + L1 anchor independently, even with the vendor's SDV offline. Only blob retrieval is gated by the vendor grant.
What this endpoint does NOT do
- Does not return subject PII. Only verification metadata. The sealed PDF contains subject data protected under BSA / GLBA / GDPR / HIPAA.
- Does not take custody. JIL is non-custodial. JIL stores no plaintext blob; the vendor's SDV does.
- Does not adjudicate access. The vendor grants and revokes. JIL enforces only what the vendor signs.
- Does not guarantee availability. Vendors control their own SDV retention. JIL enforces a 15+ year floor; if a vendor's SDV is offline, the record still verifies cryptographically.
- Does not accept POST submissions. This is a read-only public verification endpoint. Writing new records requires authenticated vendor credentials against the JIL platform API.
Evidentiary admission pathway
JIL verdict records are designed for admission under Federal Rules of Evidence 702 (expert testimony) and 901 (authentication). The cryptographic anchor authenticates the record without requiring JIL Sovereign as a fact witness - a court-appointed expert can verify the record independently.
If your court or regulatory body requires:
- A JIL officer to attest to the verification procedure under oath
- A sealed certification of verifier binary integrity
- An official transcript of the chain of custody from production to delivery
- Subpoena-compliant access to a specific record's sealed PDF
Contact contact@jilsovereign.com. Response SLA: 24 hours. For subpoena-compliant access to a sealed PDF, JIL will validate the subpoena and route to the vendor who holds the SDV blob; JIL does not possess the plaintext copy.