Build evidence file hash manifest API

Hash uploaded evidence bytes locally with md5, sha1, sha256, and sha512. Hash matches verify cryptographic integrity only, not factual authenticity.

The Build evidence file hash manifest operation is part of the OSINT & Digital Evidence Forensics API on BRAINIAC.software. Hash uploaded evidence bytes locally with md5, sha1, sha256, and sha512. Hash matches verify cryptographic integrity only, not factual authenticity. It is exposed as POST /api/v1/evidence-intelligence/file-hash-manifest and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-uploaded evidence files Caller-supplied custody events and expected hashes Limitations: Files are processed only locally in the request path and are not sent to external AI or forensic services. Cryptographic hash matches verify byte integrity only, not factual authenticity. C2PA marker presence is not a factual authenticity determination. Video keyframes are taken only from caller-supplied frame files or container metadata. Missing GPS, timestamps, and provenance fields are not invented. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Extract evidence metadata, Verify C2PA provenance markers, Build evidence chain of custody, Build image source timeline. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/evidence-intelligence/file-hash-manifest

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/evidence-intelligence/file-hash-manifest" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "files": [
    {
      "id": "EV-1",
      "filename": "scene.png",
      "mediaType": "image/png",
      "fileBase64": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg==",
      "expectedSha256": "c414cd0e204de974f73753c7e28d7638e7b3691bb8b1a2bab6b25bb7fed7ce77"
    },
    {
      "id": "EV-2",
      "filename": "scene-copy.png",
      "mediaType": "image/png",
      "role": "duplicate-candidate",
      "fileBase64": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg=="
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

OSINT & Digital Evidence Forensics APIFull docsHow it works