BRAINIAC Evidence Intelligence — Chain of Custody Builder is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).
Builds a cryptographic chain-of-custody record for digital evidence files, verifying hash integrity across custody events without sending files to external services.
Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.
Returns a structured JSON object with per-evidence items containing: ordered custody event logs (actor, action, timestamp, hash after each step), current SHA-256 hash, count of hash breaks (tampering indicators), cryptographic integrity verified flag, C2PA provenance hints, factual authenticity claim status, evidence count, overall status ('built'), findings array, and a limitations disclaimer clarifying that files are not sent externally and hash matches verify byte integrity only.
POSThttps://www.brainiac.software/api/v1/evidence-intelligence/chain-of-custody-build?utm_source=zero.xyzChoose this endpoint when you need a self-contained, privacy-preserving chain-of-custody record where files must NOT be sent to external AI or forensic cloud services. Ideal for legal, HR, law enforcement, or compliance workflows requiring cryptographic hash continuity verification across multiple handlers. Prefer over general-purpose document storage or cloud forensics APIs when auditability, tamper detection, and data locality are requirements. Best when you have structured custody event metadata (actors, timestamps, actions) to attach to file hashes.
| Field | Type | Description |
|---|---|---|
| csv | string | |
| asOf | string | |
| json | string | |
| text | string | |
| files | array | |
| custodyEvents | array | |
| expectedHashes | array |
{
"type": "json",
"example": {
"items": [
{
"events": [
{
"at": "2026-10-01T13:00:00.000Z",
"id": "CUS-1",
"note": "",
"actor": "Officer A",
"action": "collected",
"source": "",
"hashAfter": "c414cd0e204de974f73753c7e28d7638e7b3691bb8b1a2bab6b25bb7fed7ce77"
},
{
"at": "2026-10-02T09:00:00.000Z",
"id": "CUS-2",
"note": "",
"actor": "Lab B",
"action": "received",
"source": "",
"hashAfter": "c414cd0e204de974f73753c7e28d7638e7b3691bb8b1a2bab6b25bb7fed7ce77"
}
],
"filename": "scene.png",
"eventCount": 2,
"evidenceId": "EV-1",
"currentSha256": "c414cd0e204de974f73753c7e28d7638e7b3691bb8b1a2bab6b25bb7fed7ce77",
"externalAiUsed": false,
"hashBreakCount": 0,
"factualAuthenticityClaimed": false,
"externalForensicServiceUsed": false,
"cryptographicIntegrityVerified": true
}
],
"status": "built",
"findings": [],
"checkedAt": "2026-11-04T21:00:00.000Z",
"limitations": [
"Evidence bytes are processed only in this local request path. Files are not sent to external AI or forensic services.",
"Cryptographic hash matches verify byte integrity only. They do not prove factual authenticity of depicted events or authorship.",
"C2PA checks look for local provenance markers and structure hints in the uploaded bytes. Marker presence is not a factual authenticity determination.",
"Video keyframes are taken only from caller-supplied frame files or container metadata. Frames are not decoded by an external service and are not invented.",
"Location clues come from embedded metadata or labeled caller fields. Missing GPS is not invented."
],
"evidenceCount": 1,
"apiKeyRequired": false,
"externalAiUsed": false,
"paidProviderUsed": false,
"filesSentExternally": false,
"factualAuthenticityClaimed": false,
"externalForensicServiceUsed": false
}
}No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"