An AIS port directory API turns a port name into port_id before you spend quota on congestion or arrivals. On Vessels API that is GET https://vessels-api.com/api/V1/ports with header X-API-Key.
Starter is $19.99/mo (2,500 calls) with a 7-day trial. Envelope: {status,success,message,data}. MCP tools include ports_*. Docs: vessels-api.com/docs.
Request: port list
curl -H "X-API-Key: YOUR_API_KEY" \
"https://vessels-api.com/api/V1/ports"Docs do not freeze the full directory. The published numeric sibling is Buenos Aires congestion for port_id=84:
Sibling: official congestion (2026-02-09)
{
"status": 200,
"success": true,
"message": "OK",
"data": {
"port_id": "84",
"port_name": "Buenos Aires",
"period": "7d",
"snapshot": {
"timestamp_utc": "2026-02-09T10:30:00Z",
"vessels_in_anchorage": 14,
"vessels_at_berth": 9
}
}
}Resolve port_id from /ports, then call /ports/congestion or /port/expected-arrivals. There is no geofence path.
Go live
1. Register — 7-day trial.
2. Copy X-API-Key.
3. GET /api/V1/ports and cache port_id.
4. Then GET congestion for that id.
