# War-Tracker Vessel Identity by IMO

> War-Tracker Vessel Identity by IMO is a paid API for AI agents from war-tracker.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns scalar identity metadata for a single vessel by IMO number, including name, MMSI, flag, AIS type/subtype, commercial market category, dimensions, year built, and sanctions/watchlist rollups across 10 major bodies.

## Facts

- Endpoint: GET https://war-tracker.com/api/v1/vessels/:imo
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/war-tracker-com-53880cc6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MzLh7ofpeX7BPQD-QZDT2

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 war-tracker-com-53880cc6
```

Example prompt: Can you look up IMO 9299878 and tell me its vessel name, flag, AIS type, what commercial market it's in, and whether it's sanctioned or watchlisted by OFAC, EU, or the War-Tracker shadow-fleet list?

## When to prefer this

Use this endpoint when you need comprehensive vessel identity plus multi-regime sanctions/watchlist status in a single call for a known IMO number. It is the preferred choice when you need to cross-reference OFAC, EU, FCDO, UN, and shadow-fleet status simultaneously rather than querying individual sanctions databases. Choose this over the sibling sanctions-only endpoint when you also need vessel identity fields (name, flag, AIS type, market, dimensions). Best for due-diligence workflows, shipping compliance checks, and maritime risk enrichment pipelines.

## Known failure modes

- Invalid or non-existent IMO number returns 404 or empty result
- IMO number not yet indexed in War-Tracker database returns no data
- Network timeout or upstream AIS feed unavailability
- Payment failure via x402 micro-payment protocol
- Rate limiting if called too frequently
- Sanctions data may lag official list updates by hours or days

## How this service works

Single vessel identity by IMO. Returns scalar identity: name, MMSI, flag (ISO-3166-1 alpha-2), AIS type (e.g. `Tanker`, `Cargo`, `Fishing`), subtype (e.g. `Crude Oil Tanker`), commercial market (13-value enum: `WET BULK`, `DRY BULK`, `CONTAINER SHIPS`, …), overall length in metres, year built, and the boolean `sanctioned` / `watchlisted` rollups across OFAC, FCDO, EU, UANI, ASO, GAC, UN, SECO, MFAT, and the War-Tracker OSINT shadow-fleet watchlist.

Free for browsers, AI-search crawlers…

## Output

Returns a JSON object with the vessel's name, MMSI, ISO 3166-1 alpha-2 flag code, AIS type (e.g. Tanker, Cargo, Fishing), subtype (e.g. Crude Oil Tanker), commercial market from a 13-value enum (e.g. WET BULK, DRY BULK, CONTAINER SHIPS), overall length in metres, year built, and boolean sanctioned/watchlisted rollups across OFAC, FCDO, EU, UANI, ASO, GAC, UN, SECO, MFAT, and the War-Tracker OSINT shadow-fleet watchlist.

## Example request

```json
{
 "imo": "9321483"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/war-tracker-com-53880cc6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from war-tracker.com](https://www.zero.xyz/host/war-tracker.com/llms.txt)