# war-tracker.com Vessel AIS Track (1-hour polyline)

> war-tracker.com Vessel AIS Track (1-hour polyline) is a paid API for AI agents from war-tracker.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns the recent AIS position track (up to 1 hour of history) for a single vessel identified by IMO number, as an ordered list of lat/lon/speed/course points suitable for plotting.

## Facts

- Endpoint: GET https://war-tracker.com/api/v1/vessels/:imo/track
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/war-tracker-com-8ca784c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LvldCP43cEKt0Yw7glDxR

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-8ca784c8
```

Example prompt: Show me the AIS position track for the last hour for vessel IMO 9741479 — I want the ordered lat/lon points so I can plot the route on a map.

## When to prefer this

Use this endpoint when you need a time-ordered polyline of recent vessel positions to plot a movement track, rather than just the latest single position. Ideal for visualizing ship routes, detecting course changes, or confirming a vessel's recent path in a conflict or sanctions-monitoring context. Prefer over the latest-position endpoint when trajectory context matters, not just current location.

## Known failure modes

- Unknown IMO number returns empty points array or 404
- hours parameter silently clamped to 1 regardless of requested value
- Vessel not transmitting AIS — returns zero points or sparse track
- Stale data if vessel went dark — points may not reflect true position
- Rate limit or payment failure returns 402 or 429 error

## How this service works

Recent AIS position polyline for one vessel by IMO. Response shape: `{imo, hours_requested, hours_effective, raw_points_in_window, downsample_step, points: [{captured_utc, lat, lon, sog, cog}, …]}` — ordered oldest-first so a client can plot the track without sorting.

The `?hours=` parameter is currently clamped to 1 (anything wider is silently rolled back — the param stays in the route signature so we can ship longer windows as higher-priced tiers without a rename). When the raw window…

## Output

A JSON object containing the IMO, hours requested, effective hours covered, raw point count in the window, downsample step, and an array of position points ordered oldest-first, each with captured_utc timestamp, lat, lon, speed over ground (sog in knots), and course over ground (cog in degrees).

## Example request

```json
{
 "imo": "9741479"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/war-tracker-com-8ca784c8/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)