Normalize vessel identity API
Normalize caller-supplied vessel name, IMO, MMSI, call sign, flag, owner, and operator fields. Validates IMO checksum when an IMO is supplied. Paid AIS coverage is not used.
The Normalize vessel identity operation is part of the Maritime & Shipping Intelligence API on BRAINIAC.software. Normalize caller-supplied vessel name, IMO, MMSI, call sign, flag, owner, and operator fields. Validates IMO checksum when an IMO is supplied. Paid AIS coverage is not used. It is exposed as POST /api/v1/maritime-intelligence/vessel-identity-normalize and priced at $0.03 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 AIS records, vessels, waypoints, port samples, demurrage cases, cargo events, and ownership records OFAC SDN when fetchOfac is requested Limitations: 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 and are not legal determinations. Demurrage amounts use only caller-supplied laytime and rate inputs and are not legal invoices. Voyage risk reports aggregate only sections for which records were supplied or optionally fetched. 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 Detect AIS track gaps, Detect vessel route deviations, Analyze port congestion, Estimate vessel ETA. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/maritime-intelligence/vessel-identity-normalizeExample request
curl -i -X POST "https://www.brainiac.software/api/v1/maritime-intelligence/vessel-identity-normalize" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"asOf": "2026-11-04T21:00:00.000Z",
"vessels": [
{
"id": "V1",
"name": "MV Example Star",
"imo": "9074729",
"mmsi": "636019825",
"callSign": "A8AA9",
"flag": "LR",
"owner": "Example Shipping Ltd",
"operator": "Example Shipping Ltd",
"source": "Caller-supplied"
}
]
}
JSONAn 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 operations
- Detect AIS track gaps — $0.04 USDC
- Detect vessel route deviations — $0.04 USDC
- Analyze port congestion — $0.04 USDC
- Estimate vessel ETA — $0.04 USDC