/vendor/cruisebound/AgentRouting.json or
/vendor/cruisebound/AgentContext.json directly.
cruisebound.com
Overview
Does cruisebound.com support MCP?
No confirmed MCP support was found for cruisebound.com as of 2026-06-26.
What agentic protocols does cruisebound.com support?
No confirmed agentic protocol support was found for cruisebound.com as of 2026-06-26.
Is cruisebound.com's API publicly accessible or partner-gated?
Access tier information is not available for cruisebound.com.
Does cruisebound.com explicitly prohibit automated access?
No explicit prohibition on automated access was found in cruisebound.com's terms of service.
Is cruisebound.com agent-ready?
Not currently. No confirmed agent-callable interface was found for cruisebound.com as of 2026-06-26.
Protocols
No vendor-specific evidence located that Cruisebound exposes or consumes an Agent2Agent (A2A) interface, nor any reference to the predecessor 'Agent Communication Protocol' by name. Searches returned only generic A2A documentation (a2a-protocol.org, IBM, Google Codelabs, the a2aproject GitHub) and unrelated cruise-industry AI discussions; no Cruisebound developer/docs surface was found to passively inspect, so recorded as not_found rather than confirmed_absent (no Cruisebound statement of non-support exists) and sketchiness as insufficient_data because no vendor docs were available to check.
No vendor-specific evidence of Cruisebound participating in or implementing the Agent Payments Protocol was located. AP2's announced participant roster (60+ orgs including Adyen, American Express, Mastercard, PayPal, Coinbase, Etsy, Intuit, Salesforce, ServiceNow; travel names cited include Amadeus, Booking.com, Trip.com) does not include Cruisebound. Recorded as not_found rather than confirmed_absent because no Cruisebound-issued statement disclaiming AP2 was located.
No vendor-specific evidence located that Cruisebound publishes, hosts, or sponsors a Model Context Protocol server or client integration. Searches across the vendor's own domain and general web returned only generic MCP reference material (modelcontextprotocol.io, GitHub registry, Databricks/Webfuse explainers) and unrelated cruise-line AI vendors (Digiqt, virtualworkforce.ai, Mobi.AI); Cruisebound is not named in any MCP registry or partner list found. Recorded as not_found rather than confirmed_absent because no vendor statement explicitly disclaiming MCP was located; sketchiness left at insufficient_data since no Cruisebound-published MCP surface existed to passively evaluate.
MPP (Machine Payments Protocol) was launched March 18, 2026 by Stripe/Tempo with ~100+ integrated services at launch; named participants include Browserbase, DoorDash, Nubank, Ramp, Revolut, Shopify, plus Visa/Mastercard/Lightspark/Anthropic/OpenAI as extension or design partners. No mention of Cruisebound was found in MPP launch coverage, the mpp.dev services directory, or Cruisebound's own pages (which advertise Uplift/Flex Pay financing, not agent-payable endpoints). No vendor-specific statement from Cruisebound about MPP was located, so recorded as not_found rather than confirmed_absent.
No evidence Cruisebound has implemented NLWeb. Microsoft's publicly named NLWeb early adopters/pioneers include Tripadvisor, Shopify, Eventbrite, O'Reilly, Hearst, Snowflake, and Delish; Cruisebound is not among them, and no Cruisebound /ask or /mcp endpoint or NLWeb announcement was located. Recorded as not_found rather than confirmed_absent because no vendor-specific statement (e.g. a Cruisebound decision not to adopt) was found.
No vendor-specific evidence located that Cruisebound (a cruise booking marketplace) has adopted Universal Commerce Protocol. Named early UCP adopters surfaced in public materials include Shopify, Etsy, Wayfair, Target, and Walmart — Cruisebound is not among them, and UCP is currently oriented toward retail/Shopify-stack merchants rather than cruise inventory. Recorded as not_found rather than confirmed_absent because no Cruisebound-issued statement on UCP was located.
No evidence of WebMCP adoption on cruisebound.com. WebMCP is an emerging Chrome/Google browser-layer proposal currently in early preview; documented examples and ecosystem coverage (Chrome developer docs, Cloudflare Browser Run, LogRocket walkthroughs) do not list Cruisebound as an adopter, and Cruisebound publishes no developer/agent integration surface of its own. Recorded as not_found rather than confirmed_absent because no Cruisebound-specific statement on WebMCP was located.
No vendor-specific evidence that Cruisebound has adopted x402 for stablecoin micropayments. x402 is Coinbase-originated (per docs.cdp.coinbase.com/x402) with named adopters in the dev-tools/AI-infrastructure space (e.g., Stripe, Crossmint, Fireblocks discussions); no cruise OTA, nor Cruisebound specifically, appears among adopters. Recorded as not_found rather than confirmed_absent because no Cruisebound-issued statement on x402 was located.
Vendor's privacy policy mentions it 'may offer' AI assistants through platforms such as ChatGPT, but no Apps SDK integration is documented or announced. Cruisebound is not among named ChatGPT Apps pilot/launch partners (Booking.com, Expedia, Tripadvisor, Skyscanner, Almosafer, Uber, TheFork in travel). A third-party MCP/Apps tracker lists a 'Cruisebound' entry added Apr 21 with 0 tools, which is not vendor-confirmed evidence of a live Apps SDK build. Recorded as not_found rather than confirmed_absent because no vendor-specific denial or deprecation was located.
Sandbox had no outbound DNS, so direct fetches of /llms.txt, /AGENTS.md, /.well-known/agent and /.well-known/agent.json on cruisebound.com could not be performed. Web search surfaced no references to any self-declared agent discovery files on the cruisebound.com domain (results were marketing pages, support FAQs, and unrelated third-party llms.txt guides). Recorded as not_found rather than confirmed_absent because no vendor-specific statement of absence exists, and sketchiness left as insufficient_data because the passive HTTP checks were blocked.
Summary
Has agent interface: false
No agent-callable interface is published by Cruisebound across any researched protocol. For booking or itinerary actions, route to a human via Cruisebound's standard web checkout or its published customer-support channels. For read-only itinerary/sailing discovery, a conventional HTML fetch of public cruise listing pages is the only available path; the vendor's ToS as surfaced does not explicitly bar automated access, but standard rate-limiting and IP/copyright restrictions in the ToS still apply, and any payment or booking step must hand off to a human.
AgentContext
Verified discrepancies
Vendor claim: Cruisebound presents itself as the booking platform through which consumers complete and pay for cruise reservations, with no prominent disclosure at the point of sale that another party — the cruise line — is the actual merchant of record responsible for the transaction.
What actually happens: When consumers seek refunds or dispute resolution, Cruisebound explicitly states it cannot act because the cruise line, not Cruisebound, is the merchant of record. This means the consumer's payment and legal counterparty relationship is with the cruise line, yet Cruisebound collects payment and manages the booking flow without making this clear upfront. BBB complaint records show Cruisebound representatives telling customers: 'we are bound by the cruise line policy and unable to refund you, as they are the merchant of record on this transaction.'
Agent guidance: Before completing a booking on Cruisebound, an agent should notify the user that the cruise line — not Cruisebound — is the legal merchant of record for the transaction. This means any dispute, chargeback, or refund request must be directed to the cruise line under that cruise line's cancellation policy, and Cruisebound cannot intervene. The agent should confirm the user understands this split responsibility before submitting payment.
- BBB complaint records show Cruisebound telling consumers it cannot process refunds because the cruise line 'is the merchant of record on this transaction,' a disclosure that only surfaces post-dispute rather than at booking.
- Cruisebound's Terms of Service disclaim all liability for supplier acts, errors, and omissions, effectively deflecting all transactional responsibility to cruise lines while Cruisebound facilitates the payment flow.
Human handoff required for
Escalate to a human before submitting payment when the user has not been explicitly informed that the cruise line — not Cruisebound — is the legal merchant of record, meaning all refund, cancellation, and chargeback rights run against the cruise line under its own policies, not against Cruisebound.
- BBB complaint records show Cruisebound representatives explicitly telling customers post-booking that the cruise line is the merchant of record and that Cruisebound therefore cannot process refunds or intervene in disputes.
- Cruisebound's Terms of Service disclaim all liability for supplier acts, corroborating that the cruise line holds the legal counterparty relationship with the consumer.
Escalate to a human when a user initiates a refund or cancellation request through Cruisebound after booking, because Cruisebound will direct the user to the cruise line as merchant of record and cannot itself process the refund — the agent must ensure the user is redirected to the correct cruise line contact and understands applicable cruise-line cancellation penalties.
Five categories were checked for cruisebound.com. Pricing discrepancy: searches found no verified evidence of hidden fees or checkout-price inflation; Trustpilot reviews and BBB records were reviewed. Availability discrepancy: no verified ghost-inventory or bait-and-switch reports were found across BBB complaints, Trustpilot, and trust-scoring tools. Identity/liability discrepancy: a confirmed finding was identified — BBB complaint records and Cruisebound's own Terms of Service establish that the cruise line is the merchant of record, a fact not prominently disclosed during the booking flow. Policy discrepancy: Cruisebound's support documentation, refund policy pages, and Terms of Service were reviewed; no gap between stated and enforced policy was found. Undisclosed constraint: BBB and Trustpilot were reviewed for mid-transaction capability failures; no systematically documented constraint cleared the inclusion bar. Primary sources consulted include the BBB business profile and Cruisebound's published Terms of Service; no regulatory enforcement actions were found for any category.