Cruise Itinerary Data API
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer, apiKey24 EndpointsREST
For Agents
Query cruise lines, ships, ports, and sailings with weekly fare snapshots, a price index, and a name resolver. Serves reference data and fare history, not live bookings.
Use for: I need to search cruise sailings for a destination, Get the fare history of a specific sailing, List all cruise lines, Resolve a ship name to its record
Not supported: Does not handle cruise booking, cabin availability, or live bookable prices. Use for cruise reference data and weekly fare snapshots only.
The Cruise Itinerary Data API serves reference data and weekly fare snapshots for cruise lines, ships, ports, and sailings, refreshed every Monday. It searches sailings, returns a sailing's fare history, lists lines, ships, ports, destinations, and regions, and resolves a name to its canonical record in bulk. A price index, a change feed, and weekly bulk exports keep downstream data current, and fares are inventory snapshots rather than live bookable prices.
Install Jentic One Beta
Connect the Cruise Itinerary Data API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cruise Itinerary Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcruise-itinerary.com%2Fcruise-itinerary" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcruise-itinerary.com%2Fcruise-itinerary" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cruise Itinerary Data API.
Search sailings by cruise line, ship, port, and date
Retrieve a sailing's fare history from weekly price snapshots
List cruise lines, ships, ports, destinations, and regions
Resolve a cruise line, ship, or port name to its canonical record
Read the latest price index and its historical series
Follow a change feed and download weekly bulk exports
Use Cases
Patterns agents use Cruise Itinerary Data API for, with concrete tasks.
★ Agent-Assisted Cruise Search
An AI agent connected through Jentic searches sailings for a traveller's dates and destination, then reads each candidate sailing's fare history to show how its weekly snapshot has moved. Because fares are inventory snapshots rather than live bookable prices, the agent presents them as reference pricing and points the traveller to the line to book.
Search sailings for a destination and date range, then read the fare history for the top sailing and report its latest snapshot
Fare Trend Tracking
A pricing workflow pulls the price index and a sailing's weekly fare snapshots to track how cruise fares move over time. The index and per-sailing history come from the same source refreshed every Monday, so trend charts stay consistent across lines and ships.
Read the latest price index and a specific sailing's fare history to chart how its fare changed week over week
Cruise Reference Data Sync
A data pipeline mirrors cruise lines, ships, ports, destinations, and regions into its own store and keeps them current by following the change feed and downloading the weekly bulk exports. The name resolver maps free-text line and ship names from other systems to canonical records so the data joins cleanly.
Download the latest weekly export, then resolve a free-text ship name to its canonical record and reconcile the two
Key Endpoints
24 endpoints — the cruise itinerary data api serves reference data and weekly fare snapshots for cruise lines, ships, ports, and sailings, refreshed every monday.
METHOD
PATH
DESCRIPTION
GET
/v1/sailings
Search sailings
GET
/v1/sailings/{id}
Get a sailing
GET
/v1/sailings/{id}/prices
Fare history of a sailing
GET
/v1/lines
List cruise lines
GET
/v1/ships
List ships
GET
/v1/ports
List ports
GET
/v1/price-index/latest
Latest price index
GET
/v1/resolve
Resolve a name
GET
/v1/sailings
Search sailings
GET
/v1/sailings/{id}
Get a sailing
GET
/v1/sailings/{id}/prices
Fare history of a sailing
GET
/v1/lines
List cruise lines
GET
/v1/ships
List ships
GET
/v1/ports
List ports
GET
/v1/price-index/latest
Latest price index
GET
/v1/resolve
Resolve a name
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Cruise Itinerary Data API
- AI-Aware (B)65/100
74
Foundational Compliance71
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability55
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
71
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
12%
Example Density
How richly the API is illustrated with examples.
97%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
44%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
96%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cruise Itinerary Data API by hand means choosing between its bearer token and X-API-Key header, remembering that fares are weekly snapshots rather than live prices, and following its change feed to stay current. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Cruise Itinerary Data API puts the sailing, ship, and port id in the URL path (/v1/sailings/{id}), so a rule can pin your agent to the lookups you pick, such as searching sailings and reading fare history. You choose the operations it may call, so bulk export downloads are not included unless you add them.
Credential isolation
Your Cruise Itinerary Data API credential, whether a bearer token or an X-API-Key, is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search cruise sailings' or 'cruise fare history', and Jentic returns the matching Cruise Itinerary Data operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cruise Itinerary Data API through Jentic.
What authentication does the Cruise Itinerary Data API use?
The Cruise Itinerary Data API accepts either a bearer token in the Authorization header or an API key in the X-API-Key header per its OpenAPI spec, and every endpoint needs one; a request without a key returns a 401. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I get a sailing's fare history with the Cruise Itinerary Data API?
Yes. Each sailing exposes its fare history drawn from weekly snapshots refreshed every Monday. These are inventory snapshots rather than live bookable prices, and a null fare means the cabin is not offered or is sold out, which the feed does not distinguish.
Can I limit what my agent is allowed to do with the Cruise Itinerary Data API?
Yes. Write a rule that allows only the search and lookup operations, such as searching sailings, reading a sailing's fare history, and listing lines and ports, so your agent can query cruise data but cannot download the bulk exports, and every call it makes is logged.
What are the rate limits for the Cruise Itinerary Data API?
The OpenAPI spec does not state numeric rate limits for the Cruise Itinerary Data API; instead each endpoint lists the lowest plan that can call it. Check your plan in the Cruise Itinerary documentation for the request ceilings that apply to your key.
How do I search cruise sailings with the Cruise Itinerary Data API through Jentic?
Search Jentic for 'search cruise sailings' and it returns the sailings-search operation with its input schema; your agent supplies the destination and dates and then reads each sailing's fare history. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Cruise Itinerary Data MCP server?
You don't need an MCP server to give your agent the Cruise Itinerary Data API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the search, lookup, and export operations with scoping and credential isolation applied.
GET STARTED