# BRAINIAC Maritime Intelligence — Vessel Identity Normalize

> BRAINIAC Maritime Intelligence — Vessel Identity Normalize is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.03/call, status unknown (last checked 2026-11-12).

Normalizes and validates vessel identity records (IMO, MMSI, name, owner, operator, flag) from caller-supplied data, checking IMO checksums and standardizing names for maritime compliance workflows.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/maritime-intelligence/vessel-identity-normalize?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-maritime-intelligence-vessel-identity-normalize-498c9897
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UaYkBnTYFhKCe4sBxFoXb

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-vessel-identity-normalize-498c9897 -d '<json body>'
```

Example prompt: Can you normalize and validate these vessel records — I have IMO 9074729, MMSI 636019825, name 'MV Example Star', owner 'Example Shipping Ltd', flag LR — and check whether the IMO checksum is valid and the names are standardized?

## When to prefer this

Use this endpoint when you need to clean, standardize, and validate vessel identity data from your own sources — especially before sanctions screening, data deduplication, or fleet compliance workflows. It is ideal when you have caller-supplied vessel records (IMO, MMSI, name, owner, operator) and need normalized strings and IMO checksum validation without requiring a paid AIS subscription or external vessel database lookup. Prefer this over full maritime intelligence endpoints when your goal is data normalization and identity validation rather than real-time position tracking or route analysis.

## Known failure modes

- Missing required vessel identifiers (no IMO or MMSI) results in limited normalization output
- IMO checksum failures flagged but not corrected — caller must resolve
- Input exceeding 500 vessels or 200,000 character text limits returns a validation error
- Malformed base64 file content causes file parse failure
- No real-time AIS data is fetched — gaps in position data are not filled
- OFAC screening only performed if fetchOfac is explicitly requested; otherwise sanctions signals are absent

## 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 list of normalized vessel identity items, each with standardized name, owner, and operator strings, an identity key (IMO-based), IMO checksum validity flag, indicators of whether MMSI and IMO were supplied, a normalization status, any compliance findings, limitations disclaimer, and metadata including whether OFAC was fetched and whether any paid AIS provider was used.

## 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": [
   {
    "id": "V1",
    "imo": "9074729",
    "flag": "LR",
    "mmsi": "636019825",
    "name": "MV Example Star",
    "owner": "Example Shipping Ltd",
    "source": "Caller-supplied",
    "callSign": "A8AA9",
    "operator": "Example Shipping Ltd",
    "vesselType": "",
    "identityKey": "9074729",
    "imoSupplied": true,
    "paidAisUsed": false,
    "mmsiSupplied": true,
    "normalizedName": "example star",
    "normalizedOwner": "example shipping",
    "imoChecksumValid": true,
    "normalizedOperator": "example shipping"
   }
  ],
  "status": "normalized",
  "findings": [],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "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,
  "vesselCount": 1,
  "apiKeyRequired": false,
  "paidProviderUsed": false,
  "globalRealtimeCoverageClaimed": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-maritime-intelligence-vessel-identity-normalize-498c9897/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)
