How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

cruise-itinerary-com

Cruise Itinerary provides a public API delivering weekly updated cruise schedule, fare, and port data from 35 cruise lines. Users can query ships, itineraries, ports, and pricing via a simple JSON endpoint. The service is operated by Agile Travel Group, Inc. (doing business as Cruiseable) and offers free API keys with rate limits. Documentation, pricing, and legal terms are openly available.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles cruise-itinerary-com the way a machine reads it — 24 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — cruise-itinerary-com scores 57.0/100 (strong), with a separate agent-readiness read of 41/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Behind a wall

Why this profile is thin

the company serves an API surface but requires credentials before any description of it can be read

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is cruise-itinerary-com's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

What we probed
  • https://cruise-itinerary.com/openapi.json → HTTP
  • https://cruise-itinerary.com/mcp → HTTP 401
  • https://cruise-itinerary.com/ → HTTP 200

If this is out of date, tell us on the provider's repo and we will re-run the profile.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0
cruise-itinerary-com Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from cruise-itinerary-com's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/cruise-itinerary-com/"
   title="cruise-itinerary-com on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/cruise-itinerary-com.svg"
       alt="cruise-itinerary-com Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile cruise-itinerary-com

Each block below is one kind of artifact we hold for cruise-itinerary-com. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 9

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

cruise-itinerary-com Bulk exports API

The Bulk exports API from cruise-itinerary-com — 2 operation(s) for bulk exports.

cruise-itinerary-com Changes API

The Changes API from cruise-itinerary-com — 1 operation(s) for changes.

cruise-itinerary-com Cruise Itinerary Data API

The Cruise Itinerary Data API API from cruise-itinerary-com — 0 operation(s) for cruise itinerary data api.

cruise-itinerary-com Price index API

The Price index API from cruise-itinerary-com — 2 operation(s) for price index.

cruise-itinerary-com Reference data API

The Reference data API from cruise-itinerary-com — 8 operation(s) for reference data.

cruise-itinerary-com Resolver API

The Resolver API from cruise-itinerary-com — 1 operation(s) for resolver.

cruise-itinerary-com Sailings API

The Sailings API from cruise-itinerary-com — 4 operation(s) for sailings.

cruise-itinerary-com Service API

The Service API from cruise-itinerary-com — 2 operation(s) for service.

cruise-itinerary-com Ships and ports API

The Ships and ports API from cruise-itinerary-com — 3 operation(s) for ships and ports.

Scroll within the panel for all 9 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Cruise Itinerary Com Context

26 classes · 96 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

cruise-itinerary-com API Rules

18 rules · 15 errors · 2 warnings

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

ChangeEvent

14 properties

JSON SCHEMA

Cruise

12 properties

JSON SCHEMA

PortDayDetail

10 properties

JSON SCHEMA

PriceIndexPoint

14 properties

JSON SCHEMA

SailingDetail

16 properties

JSON SCHEMA

Sailing

15 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cruise Itinerary Com Authentication

apiKey/http · 2 schemes

SECURITY

Cruise Itinerary Com Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Cruise Itinerary Com Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Cruise Itinerary Com Agentic Access

24 operations · 1 acting

24 operations · 1 acting

AGENTIC

Resources

Every other property we hold for cruise-itinerary-com — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Access & Security 2

Authentication, authorization, and security posture

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/cruise-itinerary-com · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of cruise-itinerary-com, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.