ShipXY Maritime Data API

Engineering maritime data queries

When tracking vessels, estimating port arrivals, or planning reference routes, the hard part is not calling a single API. It is handling vessel identity disambiguation, five-digit port codes, tide station IDs, time windows, area polygons, and permission limits in one consistent workflow. This skill wraps 33 ShipXY maritime services into a controlled CLI process: read each service's semantic contract, validate parameters, execute the call, and interpret the response according to documented rules, instead of hand-rolling requests with inconsistent semantics.

From lookup to operational insight

Core capabilities include searching vessels by MMSI, IMO, name, or call sign and distinguishing same-name vessels; querying latest single-vessel or multi-vessel AIS positions, speed, course, and nearby vessels within about 10 nautical miles; reading current snapshots inside polygons or fixed fleets; retrieving registry, flag, and Lloyd's profile data; analyzing historical tracks, approach events, and port calls; resolving five-digit port codes and querying berthed, anchored, arriving, and historical port activity; obtaining single-vessel ETA and port-to-port reference routes; and checking weather, typhoons, tides, and navigational warnings.

Key workflow rules matter: skip vessel search when a trusted MMSI is already known; resolve port names through port search before use; keep tide station IDs separate from port codes; do not use current area snapshots as historical discovery; run a dry-run check for broad, spatial, or historical queries; and read large responses from files via result_path rather than dumping them into chat.

Boundaries and cautions

This skill is useful for auditable maritime workflows such as vessel monitoring, port operations analysis, route pre-planning, and ocean-condition checks. It is not a navigation system: route outputs are planning references only and must not be treated as navigation instructions, safety authorization, or collision-avoidance advice. Several endpoints have explicit limits, such as approach-event windows of up to 31 days and port-call lists of up to 7 days per request. Area polygons should use ordered lng,lat points, with pagination handled where required. Results also depend on permissions, history depth, quota, and freshness, so reports should preserve timestamps, time zones, units, sentinel values, and pagination status.