A vessel search API turns a name fragment into IMO / flag / type JSON before you spend quota on a live position. On Vessels API that is GET https://vessels-api.com/api/V1/vessels/search with header X-API-Key. The docs example uses query=atlantic, flag=Panama, and per_page=20. The envelope is always {status, success, message, data}.
Starter is $19.99/mo (2,500 calls) with a 7-day trial. Eighteen REST paths share the key; /vessel/live-position is Professional+ with a separate quota. Docs: vessels-api.com/docs. MCP: https://mcp.vessels-api.com.
Request: search “atlantic”
curl -H "X-API-Key: YOUR_API_KEY" \
"https://vessels-api.com/api/V1/vessels/search?query=atlantic&flag=Panama&per_page=20"
Response: official docs sample
{
"status": 200,
"success": true,
"message": "OK",
"data": {
"vessels": [
{
"imo": "9702510",
"mmsi": null,
"name": "ZJ ATLANTIC",
"flag": "Liberia",
"vessel_type": "Bulk Carrier",
"gross_tonnage": "50420",
"deadweight_tonnage": "60200",
"year_built": "2010",
"length_m": 294.0,
"width_m": 32.0
}
],
"pagination": {
"current_page": 1,
"per_page": 20,
"total": 150,
"last_page": 8
}
}
}
Note the sample row is flagged Liberia even though the query passed flag=Panama — treat the JSON as the source of truth. mmsi is null here; do not invent an MMSI. Pagination total is 150 in the fixture.
MCP
The same search sits on the Vessels MCP catalog (tools include search, track, nearby, ports, positions). Point the client at https://mcp.vessels-api.com with the REST key. Quota matches REST.
Go live
1. Register — 7-day trial.
2. Copy X-API-Key.
3. GET search with query=atlantic.
4. Take data.vessels[].imo into track / position calls.
FAQ
MarineTraffic or VesselFinder?
Those are competitor H1s from earlier posts. This endpoint is first-party REST search on Vessels API.
