# BRAINIAC Maritime Intelligence — Cargo Shipment Event Reconcile

> BRAINIAC Maritime Intelligence — Cargo Shipment Event Reconcile 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-14).

Reconciles cargo shipment events against operational AIS data, documents, and compliance signals to identify discrepancies, sanctions matches, and demurrage findings

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/maritime-intelligence/cargo-shipment-event-reconcile?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-maritime-intelligence-cargo-shipment-event-reconcile-f8304340
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JhR4P4fU-Cv6Gx0kyaglP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-maritime-intelligence-cargo-shipment-event-reconcile-f8304340 -d '<json body>'
```

Example prompt: I need to reconcile shipment SH1 with bill of lading BL1 — the cargo was loaded at Singapore on 2026-11-01. Cross-check the event against the AIS positions I'm supplying for vessel IMO 9123456 and flag any quantity mismatches or OFAC sanctions signals.

## When to prefer this

Use this endpoint when you need to reconcile cargo shipment documentary events (bills of lading, loading/discharge records) against vessel AIS position data and want integrated OFAC sanctions screening — all without needing a paid AIS subscription or API key. Prefer this over manual document review or siloed compliance tools when you have structured shipment event data and want a single-call audit trail with explicit data provenance limitations disclosed.

## Known failure modes

- Missing required cargo event data results in empty items array with unreconciled status
- Vessel IMO/MMSI not supplied means sanctions and AIS matching cannot be performed
- AIS points with gaps produce track-gap findings rather than confirmed positions
- Quantity mismatches flagged as findings but not auto-resolved
- OFAC fetch may be unavailable or return stale data; fetchOfac must be explicitly requested
- Input CSV/JSON exceeding 200,000 characters will be rejected
- Sanctions signals are name/IMO comparisons only and are not legal determinations

## How this service works

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.

## Output

Returns a JSON object with an array of reconciled event items (each with event type, shipment ID, bill of lading, quantity match flag, and reconciliation status), overall reconciliation status, a list of findings or anomalies, counts of reconciled events, flags indicating whether OFAC data or paid AIS was used, and a detailed limitations section clarifying data provenance and coverage.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "fileBase64"
   ],
   "properties": {
    "role": {
     "type": "string",
     "maxLength": 80
    },
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json",
      "application/octet-stream"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "fileBase64"
    ],
    "properties": {
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "filename": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
     },
     "mediaType": {
      "enum": [
       "text/plain",
       "text/csv",
       "application/json",
       "application/octet-stream"
      ],
      "type": "string"
     },
     "fileBase64": {
      "type": "string",
      "maxLength": 12000000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20
  },
  "vessels": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "imo": {
      "type": "string",
      "maxLength": 20
     },
     "flag": {
      "type": "string",
      "maxLength": 80
     },
     "mmsi": {
      "type": "string",
      "maxLength": 20
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "owner": {
      "type": "string",
      "maxLength": 200
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "callSign": {
      "type": "string",
      "maxLength": 40
     },
     "operator": {
      "type": "string",
      "maxLength": 200
     },
     "vesselType": {
      "type": "string",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "maxItems": 500
  },
  "aisPoints": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "at": {
      "type": "string",
      "maxLength": 40
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "key": "sh1|loaded|2026-11-01|sgsin",
    "opsAt": "2026-11-01",
    "source": "Caller-supplied; Caller-supplied",
    "eventType": "loaded",
    "documentAt": "2026-11-01",
    "opsEventId": "C2",
    "reconciled": true,
    "shipmentId": "SH1",
    "billOfLading": "BL1",
    "quantityMatch": true,
    "documentEventId": "C1"
   }
  ],
  "status": "reconciled",
  "findings": [],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "eventCount": 1,
  "limitations": [
   "Vessel identities, AIS points, waypoints, port samples, demurrage cases, sanctions entries, cargo events, and ownership records are copied only from labeled fields supplied by the caller, or from the key-free public OFAC SDN publication when fetchOfac is requested.",
   "No paid AIS service is used and no API key is required. Global real-time vessel coverage is not claimed.",
   "Track gaps, route deviations, and ETA values use only supplied positions/speeds and simple geodesic math. Missing values are not invented.",
   "Sanctions signals are name/IMO comparisons only. Exact matches are labeled as signals, not confirmed legal determinations. Possible matches require human review.",
   "Demurrage amounts use only caller-supplied laytime and rate inputs and are not legal invoices."
  ],
  "ofacFetched": false,
  "paidAisUsed": false,
  "apiKeyRequired": false,
  "reconciledCount": 1,
  "paidProviderUsed": false,
  "globalRealtimeCoverageClaimed": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-maritime-intelligence-cargo-shipment-event-reconcile-f8304340/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
