Cross-reference public investigations API

Cross-reference subjects across court, enforcement, and notice records while preserving non-judgment statuses and never inferring guilt.

The Cross-reference public investigations operation is part of the Public Records, Crime & Regulatory Intelligence API on BRAINIAC.software. Cross-reference subjects across court, enforcement, and notice records while preserving non-judgment statuses and never inferring guilt. It is exposed as POST /api/v1/public-records/investigation-cross-reference and priced at $0.05 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-supplied court, enforcement, crime, incident, and notice records Public feed when feed.url is requested Limitations: No paid public-records provider is used and no API key is required. Allegations, investigations, charges, penalties, and final judgments are labeled separately. Guilt is never inferred. An allegation, investigation, or charge is never treated as a conviction or final judgment. Missing counts, penalty amounts, and dispositions are not invented. Public feed items are used only when a feed URL is supplied. 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 Normalize court decision records, Extract court case timelines, Search regulatory enforcement actions, Compare public crime statistics. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/public-records/investigation-cross-reference

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/public-records/investigation-cross-reference" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "businessName": "Example Co",
  "courtRecords": [
    {
      "id": "CRT-1",
      "caseNumber": "22-CV-100",
      "title": "City v Example Co",
      "businessName": "Example Co",
      "parties": [
        "Example Co"
      ],
      "status": "charge",
      "date": "2026-01-10"
    }
  ],
  "enforcementActions": [
    {
      "id": "ENF-1",
      "authority": "Regulator A",
      "subject": "Example Co",
      "businessName": "Example Co",
      "action": "investigation opened",
      "status": "investigation",
      "date": "2025-11-01"
    }
  ],
  "notices": [
    {
      "id": "NTC-1",
      "agency": "City Police",
      "title": "Notice mentioning Example Co",
      "body": "Example Co is referenced in a public advisory. No judgment is stated.",
      "status": "notice",
      "date": "2026-02-01"
    }
  ]
}
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

Public Records, Crime & Regulatory Intelligence APIFull docsHow it works