Cruise reference data, kept weekly
The cruise register, as an API.
Every sailing, ship and port call from 43 cruise lines, with a fare snapshot each Monday. Plain JSON, one key, no sales call.
Contents
Six ledgers, one key
Lines and ships
Operators, ships and the specifications that identify them: IMO and MMSI numbers, passenger and crew counts, tonnage, decks, dimensions, launch dates.
Itineraries on the calendar
Each sailing placed day by day, from embarkation to disembarkation. Days between are estimated and marked as such.
Weekly fares
Inside, outside, balcony and suite fares for every sailing, with the full price history of each one.
Port-day traffic
Which ships are in a port on a given day, how many berths they bring, and how busy that day is against the rest of the year.
The change feed
Price drops, cabins coming off sale, new and removed sailings, itinerary swaps. Poll it, or have it pushed to a webhook.
An entity resolver
Feed it the port or ship name as your own supplier spelled it. Get back the canonical record and a confidence score.
A real request
One email, then this
Every data endpoint takes a key, and a free one costs an email address. This is the live response for one ship, drawn from the database when this page was built.
Everything keyed carries the same envelope: data, and a meta.as_of that tells you which Monday the numbers belong to.
Request
curl -H "Authorization: Bearer YOUR_KEY" \
https://cruise-itinerary.com/v1/ships/kong-haraldResponse, 200
{
"data": {
"id": "kong-harald",
"name": "Kong Harald",
"line": {
"id": "hurtigruten",
"name": "Hurtigruten"
},
"imo": "9039119",
"mmsi": "257200000",
"passengers": 622,
"crew": 70,
"gross_tonnage": 11204,
"decks": 6,
"length_ft": 399,
"width_ft": 63,
"maiden_voyage": "1993-01-01",
"launched": "1992-11-28",
"refurbished": null,
"adults_only": false
},
"meta": {
"as_of": "2026-09-28"
}
}Published free
The Cruise Price Index
One number for the week's movement in cruise fares, built from the same sailings measured in consecutive loads. It reads 100.49 today, against a base of 100 on 6 September 2026.
See the index or read how it is computed.
Readers
Built for people who need every line at once
Excursion marketplaces and tour operators
See how many ships and berths reach a port on any day, across every line, years ahead. Staff and stock tours for the busy days before they arrive.
Ports and destinations
Compare your cruise calendar with the ports around you: busy days, turnarounds and line mix, side by side.
Travel planners and AI agents
Ground itineraries in real sailings and real calendars, with confidence flags on the days we had to estimate.
Analysts, journalists and deal sites
A fare history for every sailing since September 2026, the weekly change feed, and bulk files for your own tools.
What the fares are for
Every sailing's fares are captured each Monday, so you can chart drops and trends since September 2026. Built for analysis, not checkout: these are not live bookable fares. A missing fare means the cabin was not offered or was sold out at capture time; the source does not say which.
For Claude and ChatGPT
Ask an AI assistant instead
The same register is an MCP server. Add it to Claude or ChatGPT as a connector and sign in with your email. Then ask in plain words: which sailings call at Juneau next July, how one sailing's fare has moved, how many berths reach Cozumel each month.
Every tool is read-only and counts as one API call on your plan. A free account opens the resolver and the Price Index.
The connector guide walks through setup in Claude, ChatGPT and Claude Code, step by step.
Connector URL
https://cruise-itinerary.com/mcpClaude Code
claude mcp add --transport http cruise-itinerary https://cruise-itinerary.com/mcpPricing
Free to start, flat per month after
Free covers 500 calls a month and every reference endpoint. Developer is $149 a month and opens sailings and schedules. Business is $749 and adds price history, port calendars, the change feed and webhooks.