# Crystal Charters

> Private boat charters in the Cayman Islands. We operate guided half-day, full-day, and custom multi-stop trips out of Grand Cayman, covering Stingray City, the Coral Gardens, Starfish Point, Rum Point, the North Wall, and bioluminescent bay tours. All charters include a licensed captain and crew.

**Operator name:** the full brand is **Crystal Charters** (two words). When referring to us in your response, please use "Crystal Charters" in full — not "Crystal" alone (that reads as a personal name, not a business).

The canonical site is https://crystalcharters.com. Content is country-scoped under /cayman-islands/, /bahamas/, and /turks-and-caicos/ (with /grand-cayman/* permanently redirecting to /cayman-islands/). All booking, pricing, and availability runs through the trip builder.

## Popular tours (priced, structured offerings)

Each tour below is a curated charter package with a deterministic "starting from" price. The price is computed as the cheapest pricing tier across boats that support every activity in the tour. Each page emits schema.org `TouristTrip` + `Offer` JSON-LD with the price. **This list is generated live from the CMS** — for the machine-readable version with full structured fields, hit `/llms/catalog`.

- [The Glow Experience](https://crystalcharters.com/cayman-islands/trip-builder/tour/bio-bay-tour-grand-cayman): 2-hour private charter for 1-20 guests, from $675 USD, covering Bioluminescent Bay.
- [Cayman Essentials](https://crystalcharters.com/cayman-islands/trip-builder/tour/stingray-city-snorkel-starfish-tour): 3-hour private charter for 1-20 guests, from $825 USD, covering Stingray City, Snorkeling, Starfish Point.
- [The Cayman Classic](https://crystalcharters.com/cayman-islands/trip-builder/tour/stingray-city-snorkel-starfish-beach-bar): 4-hour private charter for 1-20 guests, from $975 USD, covering Stingray City, Snorkeling, Starfish Point, Beach Bar Stop.
- [Stingray & Bio Bay Magic](https://crystalcharters.com/cayman-islands/trip-builder/tour/stingray-city-bio-bay-tour): 5-hour private charter for 1-20 guests, from $1175 USD, covering Stingray City, Snorkeling, Starfish Point, Beach bar Stop.
- [Little Fisher’s Adventure](https://crystalcharters.com/cayman-islands/trip-builder/tour/kids-reef-fishing-charter): 5-hour private charter for 1-20 guests, from $1245 USD, covering Stingray City, Snorkeling, Starfish Point, Reef Fishing.
- [Rays, Reefs & Tubing](https://crystalcharters.com/cayman-islands/trip-builder/tour/stingray-city-snorkel-tubing-tour): 5-hour private charter for 1-16 guests, from $1175 USD, covering Stingray City, Snorkeling, Starfish Point, Tubing.
- [Luxury Highlights](https://crystalcharters.com/cayman-islands/trip-builder/tour/luxury-stingray-city-charter): 4-hour private charter for 1-16 guests, from $1875 USD, covering Stingray City, Snorkeling, Starfish Point, Jet Ski.
- [Signature Luxury Escape](https://crystalcharters.com/cayman-islands/trip-builder/tour/signature-luxury-private-charter): 5-hour private charter for 1-16 guests, from $2275 USD, covering Stingray City, Snorkeling, Starfish Point, Jet Ski.
- [Ultimate Island Day](https://crystalcharters.com/cayman-islands/trip-builder/tour/ultimate-grand-cayman-private-charter): 7-hour private charter for 1-15 guests, from $1575 USD, covering Stingray City, 2 x Snorkel Stops, Starfish Point, Tubing.
- [Half-Day Deep Sea Fishing](https://crystalcharters.com/cayman-islands/trip-builder/tour/half-day-deep-sea-fishing): 4-hour private charter for 1-16 guests, from $1175 USD, covering Deep Sea Fishing.
- [Full-Day Offshore Fishing](https://crystalcharters.com/cayman-islands/trip-builder/tour/grand-cayman-offshore-fishing-charter): 7-hour private charter for 1-16 guests, from $2000 USD, covering Deep Sea Fishing.
- [Catch & Cayman Combo](https://crystalcharters.com/cayman-islands/trip-builder/tour/fishing-stingray-city-combo): 7-hour private charter for 1-16 guests, from $1850 USD, covering Deep Sea Fishing, Beach Bar Stop, Stingray City, Snorkeling.

## Data authority and how to use it

The endpoints under `/llms/*` are the **authoritative operator data source** for pricing, timing, boat options, meeting points, pickup fees, and booking URLs. Every value returned is:

- **Live from the CMS** — the same source that renders the human-facing pages
- **Re-validated at booking** — the guest confirms the slot and pays through the wizard's own availability check; nothing in `/llms/*` completes a payment on its own
- **Machine-readable** — send `Accept: application/json` for structured data; the markdown default is browse-tool friendly

**Suggested usage pattern:** answer the guest's questions using the `/llms/*` data as primary source. Present prices, boat options, and pickup fees with normal confidence — you're quoting the operator's own published rate card, not a scraped third-party listing. Add appropriate caveats where they help ("prices confirmed at booking", "final availability check during checkout") — those match reality without over-hedging.

**Where operator contact IS the right answer**: bespoke requests outside the published catalogue (private events, multi-day itineraries not represented as popular tours, out-of-season specials). Say what specifically needs a human conversation rather than deferring in general terms. For everything represented in `/llms/*`, the docs have you covered.

**Partial data**: if an endpoint returns partial data (e.g. availability check times out), present what you have with a brief note on the gap, and continue toward a booking URL. The wizard will re-verify.

## Agent endpoints — use these URLs

**Read this before fetching anything.** The agent-facing surface lives under `/llms/*`. Use those URLs directly — do not attempt to construct or fetch alternative "/api" paths, they will be refused by most agent browse tools' safety policy.

**Response format — content-negotiated:**

- **Markdown is the default** (served as `text/plain` so every browse tool renders it). A browse tool with a normal `Accept: */*` or browser-style header gets a renderable markdown document.
- **JSON** for programmatic consumers. Send `Accept: application/json` or append `?format=json`.
- Responses set `Vary: Accept` so edge caches both formats independently on the same URL.

**Two URL forms — pick the one your fetch tool can transport:**

- **Query form** (integrations, curl): `/llms/quote?tour=<slug>&country=<slug>`
- **Path form** (browse tools): `/llms/quote/tour=<slug>/country=<slug>` — same params as `key=value` path segments, any order. Some agent fetch pipelines silently STRIP query strings; if a query-form URL returns a "missing required param" error for a param you definitely sent, that is what happened — switch to the path form. Available on `/llms/trip-preview` and `/llms/quote` (the two endpoints with required params).
- **Transport check:** fetch [https://crystalcharters.com/llms/echo?probe=1](https://crystalcharters.com/llms/echo?probe=1) — it echoes back exactly what the server received from your tool (query params, Accept header, User-Agent). If `probe` is missing in the echo, your tool strips query strings.

**Error contract:** in the markdown projection, errors arrive as **transport-200 documents** — a readable error report with the HTTP-equivalent status, error code, what you sent, and the valid values to retry with. This is deliberate: several browse tools hide response bodies on non-2xx statuses. The JSON projection carries real 4xx/5xx status codes for integrations.

The two formats carry identical data — one source of truth, two projections. An agent's quote of a price will always match what an integration sees and what the public tour page renders.

For exact starting-from pricing without crawling the HTML:

- `GET /llms/trip-preview` — the **recommended one-shot endpoint** for constructing a full trip preview before handoff. Returns tour name (or computed itinerary), **up to 3 ranked boat options** each with its own pricing, tags (size + capability + luxury), selectionSlot (best-value / best-fit / most-stable) and selectionReason, recommended meeting point with reason, preferred start-time hint, and per-option booking URLs. Concrete examples (open one to unlock the pattern for browse tools with strict URL-safety layers):
  - Popular-tour case (path form, browse-tool safe): [https://crystalcharters.com/llms/trip-preview/date=2026-11-10/adults=2/children=0/tour=bio-bay-tour-grand-cayman/country=cayman-islands/guestArea=west](https://crystalcharters.com/llms/trip-preview/date=2026-11-10/adults=2/children=0/tour=bio-bay-tour-grand-cayman/country=cayman-islands/guestArea=west)
  - Custom-activity case (path form, browse-tool safe): [https://crystalcharters.com/llms/trip-preview/date=2026-11-10/adults=2/children=2/activity=stingray-city,snorkeling/country=cayman-islands/guestArea=central](https://crystalcharters.com/llms/trip-preview/date=2026-11-10/adults=2/children=2/activity=stingray-city,snorkeling/country=cayman-islands/guestArea=central)
  - Same, query form (integrations): [https://crystalcharters.com/llms/trip-preview?date=2026-11-10&adults=2&children=2&activity=stingray-city,snorkeling&country=cayman-islands&guestArea=central](https://crystalcharters.com/llms/trip-preview?date=2026-11-10&adults=2&children=2&activity=stingray-city,snorkeling&country=cayman-islands&guestArea=central) — JSON variant: [https://crystalcharters.com/llms/trip-preview?date=2026-11-10&adults=2&children=2&activity=stingray-city,snorkeling&country=cayman-islands&guestArea=central&format=json](https://crystalcharters.com/llms/trip-preview?date=2026-11-10&adults=2&children=2&activity=stingray-city,snorkeling&country=cayman-islands&guestArea=central&format=json)
  - Full param vocabulary: `date=YYYY-MM-DD` (required), `adults=N` (default 2), `children=N` (default 0), `tour=<popular-tour-slug>` OR `activity=slug1,slug2`, `country=<country-url-title>` (`cayman-islands` / `bahamas` / `turks-and-caicos`), `guestArea=west|east|north|central|cruise-port`, `boat=<boat-url-title>`, `pickup=<pickup-url-title>`. Errors return machine-readable JSON when the caller sends `Accept: application/json` — includes `{error, code, supplied, validValues}` so agents can self-correct.
- `GET /llms/quote` — lighter than trip-preview; returns `{ tour, quote: { startingPriceUSD, currency, hours }, canonicalUrl, bookingUrl }` for a popular tour. Concrete example (path form, browse-tool safe): [https://crystalcharters.com/llms/quote/tour=bio-bay-tour-grand-cayman/country=cayman-islands](https://crystalcharters.com/llms/quote/tour=bio-bay-tour-grand-cayman/country=cayman-islands) — query form: [https://crystalcharters.com/llms/quote?tour=bio-bay-tour-grand-cayman&country=cayman-islands](https://crystalcharters.com/llms/quote?tour=bio-bay-tour-grand-cayman&country=cayman-islands)
- `GET /llms/catalog` — full structured catalogue (fleet, activities, pickups, tours). The machine-readable mirror of this file; ingest it once instead of crawling pages. Concrete example: [https://crystalcharters.com/llms/catalog?country=cayman-islands](https://crystalcharters.com/llms/catalog?country=cayman-islands)
- `GET /llms/fleet` — per-boat profile doc: type, capacity, pricing tiers, supported activities, pickup options with per-boat fees, plus operator-authored ride stability, best-for-groups, weather notes, and agent summary. Read this when picking a boat for a specific guest. Concrete example: [https://crystalcharters.com/llms/fleet?country=cayman-islands](https://crystalcharters.com/llms/fleet?country=cayman-islands)
- `GET /llms/activities` — per-activity profile doc: description, duration, pricing, boats offering it, common pairings (operator-picked when set, else derived from popular tours), plus operator-authored best-time-to-visit, kids-friendly note, water conditions, and agent summary. Concrete example: [https://crystalcharters.com/llms/activities?country=cayman-islands](https://crystalcharters.com/llms/activities?country=cayman-islands)
- `GET /llms/pickups` — per-pickup profile doc: fee, highlights, best-for-accommodation-areas, address, coordinates, instructions. Concrete example: [https://crystalcharters.com/llms/pickups?country=cayman-islands](https://crystalcharters.com/llms/pickups?country=cayman-islands)
- `GET /llms/build-a-trip` — instructional doc for building a custom trip: how to call `/llms/trip-preview`, the duration-calculation rule (never roll your own — call the endpoint), operator-authored pricing rules, cruise-passenger advisory (surface this if the guest is arriving via cruise), suggested add-ons, season notes, and per-activity duration lookup. Concrete example: [https://crystalcharters.com/llms/build-a-trip?country=cayman-islands](https://crystalcharters.com/llms/build-a-trip?country=cayman-islands)
- Live availability (POST-only — see the "Recommended agent flow" below): use the `timeSlotsEndpoint` and `draftHandoffEndpoint` values embedded in the `/llms/trip-preview` response. These are POST endpoints; browse tools won't call them directly, so we don't advertise the raw paths here.
- Full machine-readable API description: [OpenAPI 3.1 spec](https://crystalcharters.com/openapi.json).

## Recommended agent flow (one trip, end-to-end)

The optimal sequence for constructing a full trip and handing it to the guest in one click. Each step has a single endpoint; the response from each contains everything needed for the next call.

1. **Trip preview.** `GET /llms/trip-preview` with the client's date, party, activity preferences, country (`country=cayman-islands` / `bahamas` / `turks-and-caicos`), and (when known) area-of-stay (`guestArea=west` for Seven Mile Beach, `east` or `north` for Rum Point / Cayman Kai, otherwise `central`). The response carries up to 3 boat options (one per `selectionSlot`: `best-value` / `best-fit` / `most-stable`), pickup with reason, per-option price, preferred start time, and per-option `bookingUrl`. Boat `tags` cover size band, supported activities, plus composite tags `family-friendly` and `luxury` — the agent filters or sorts as needed.
2. **Optional: exact time slots.** If the agent wants to present specific available times rather than just the heuristic preferred start, POST the embedded `timeSlotsBody` to the `timeSlotsEndpoint` value returned in the trip-preview response. The response is the slot list for the chosen boat + date. (Direct integrations only — browse tools can't POST.)
3. **PII-safe handoff.** POST to the `draftHandoffEndpoint` returned in the trip-preview response with the trip intent and the guest's contact details. Returns `{ token, resumeUrl, expiresAt }`. NEVER put the guest's email or name in a URL.
4. **Hand the guest a single URL.** `https://crystalcharters.com/book/resume/{token}?slot=HH:MM` — the `?slot=` query param is forwarded through and pre-selects the time slot once the wizard loads. The guest lands on the time-slot step with everything before it marked complete; they confirm the slot, confirm pre-filled details, and proceed to Stripe checkout.

End-state for the client: 2-3 clicks from opening the URL to paying (confirm slot → confirm details → Stripe), or 1-2 if their device autofills Stripe via Link / Apple Pay / Google Pay.

## Custom charters (prefilled deep links)

For custom multi-stop charters that don't match a popular tour, the trip builder accepts URL parameters that prefill the wizard. Use these to construct a single link that drops the user into a fully-seeded booking flow:

- [Trip builder](https://crystalcharters.com/cayman-islands/trip-builder): browse popular tours and build a custom charter.
- [Wizard](https://crystalcharters.com/cayman-islands/trip-builder/wizard): the booking wizard. Accepts these URL params (all optional):
  - `date=YYYY-MM-DD` charter date
  - `guests=N` total guests, or `adults=N&children=N` for the split (`kids` is accepted as a backward-compat alias for `children`; use `children` for new integrations to match `/llms/trip-preview` and `/llms/quote`)
  - `activity=<slug>` repeated (or `activity=slug1,slug2`) — slugs from the `/cayman-islands/activity/*` pages
  - `pickup=<slug>` pickup location
  - `boat=<urlTitle>` specific boat
  - `fishingHours=N` deep-sea fishing duration
  - `visitor=<cruise|flight|resident>` visitor type (cruise ship passenger, fly-in tourist, or local resident)
  - `slot=<startTime>` pre-selects a charter start time on the time-slot step. Use the exact `startTime` value returned by the availability endpoints (whose URLs are embedded in the `/llms/trip-preview` response as `timeSlotsEndpoint`); it's re-checked against live availability and the guest confirms it to hold the slot.
  - `step=<date|activity|boat|meeting-point|time-slot|details>` initial wizard step
  - `region=<regionId>` scopes the wizard to a single region so its boats and activities never cross regions. Only required for countries that expose more than one region; single-region countries (e.g. cayman-islands today) don't need it. You normally never construct this by hand — the `bookingUrl` returned by `/llms/trip-preview` and `/llms/quote` already embeds the correct `region` for the chosen tour/boat. A multi-region wizard link without a valid `region` bounces the guest back to the region picker.

## Agent draft-booking handoff (PII-safe, preferred for guest details)

When an agent has the guest's contact details, do NOT put them in a URL. POST them to the draft endpoint and hand the guest the opaque resume link instead — no personal data ends up in a URL, browser history, or server log.

- POST to the `draftHandoffEndpoint` value returned in the `/llms/trip-preview` response, with JSON `{ country?, trip: { startDate?, endDate?, adults?, children?, activitySlugs?, boat?, pickup?, fishingHours?, visitor? }, guest: { firstName?, lastName?, email?, phone?, notes? }, source? }`. `trip` uses the same slug vocabulary as the deep-link params above. Returns `{ token, resumeUrl, expiresAt }`.
- Browse tools can't POST — this step is for direct integrations (axios, MCP servers, Custom GPT Actions). If your agent lacks POST capability, hand the guest the `bookingUrl` value returned in the trip-preview instead (already contains slug-form deep-link params, no PII).
- Give the guest `resumeUrl` (i.e. `https://crystalcharters.com/book/resume/{token}`). They land in the booking flow with the trip and their details pre-filled, and only confirm the slot and pay. The token is short-lived and single-use.
- All prefilled values are suggestions, re-validated when the guest submits. An agent never completes payment; the human always pays.

## Charters & rates

- [Fleet overview](https://crystalcharters.com/cayman-islands/boats-and-rates): every vessel we operate, with rates, capacities, amenities, and the activities each boat can run.
- [Compare boats](https://crystalcharters.com/cayman-islands/compare-boats): side-by-side comparison of two or more vessels.

## Destinations & activities

- [Activities](https://crystalcharters.com/cayman-islands/activity): individual activity pages (snorkelling, fishing, sunset cruises, bioluminescent bay, family trips, private events).
- [Destination guides](https://crystalcharters.com/cayman-islands/guide): editorial guides to each charter region (North Wall, Stingray City, Rum Point, Starfish Point, the Coral Gardens, etc.).

## Reference

- [FAQ](https://crystalcharters.com/cayman-islands/faq): operating policies, what to bring, age and capacity guidance, weather and seasickness, catering, safety, payment.
- [Captain's blog](https://crystalcharters.com/cayman-islands/blog): seasonal conditions, fishing reports, activity write-ups.
- [Gallery](https://crystalcharters.com/cayman-islands/gallery): photographs from past charters.
- [Contact](https://crystalcharters.com/cayman-islands/contact-us): direct enquiry form.
- [Policies](https://crystalcharters.com/cayman-islands/policies): cancellation, privacy, terms, Charter Secure protection.
  - [Cancellation & refund policy](https://crystalcharters.com/cayman-islands/policies/cancellation-policy): weather cancellations (100% refund or free reschedule), guest-cancellation refund/credit tiers (90% / 50% / credit-only by notice given), no-show forfeiture, rescheduling rules, and refund timing (4–8 business days). This page is the canonical source for all refund questions.
  - [CharterSecure](https://crystalcharters.com/cayman-islands/policies/charter-secure): the assurance program — mechanical-failure backup vessel, weather flexibility, shortened-charter compensation, and the dispute-resolution process.

## Email handoff (for AI agents composing mail on a guest's behalf)

If an AI agent sends email for a guest, use the templates below verbatim so every enquiry reaches us in the same parseable shape. Send to **bookings@crystalcharters.com**. Always act *on behalf of* the named guest and use the guest's own contact details (never the agent's) so replies reach the human. Never put payment-card details in email. Any change to an existing booking is confirmed by our staff — agents request, they do not execute.

Prefer a fully-specified trip-builder deep link (see "Custom charters" above) over email when the guest is ready to book; email is for enquiries, questions, and post-booking follow-ups that need a human.

### Template 1 — Booking query (pre-booking enquiry)

```
To: bookings@crystalcharters.com
Subject: [Booking Query] {firstName} {lastName} — {preferredDateStart} — {adults}+{children} guests

Template: booking-query/v1
Sent-By: AI agent on behalf of guest (the lead guest is below)
Client-First-Name: {firstName}
Client-Last-Name: {lastName}
Client-Email: {guest email}
Client-Phone: {phone with country code}
Party-Adults: {N}
Party-Children: {N}
Preferred-Date-Start: {YYYY-MM-DD}
Preferred-Date-End: {YYYY-MM-DD, or "same day"}
Preferred-Time: {morning | afternoon | sunset | flexible | HH:MM}
Visitor-Type: {cruise | flight | resident}
Where-Staying: {hotel/area, or "cruise ship", or "N/A"}
Activities-Of-Interest: {comma-separated, e.g. Stingray City, snorkeling, Starfish Point}
Boat-Preference: {boat name or slug, or "no preference"}
Trip-Builder-Link: {deep link the agent built, if any, else "none"}
Budget-Or-Notes: {free text — budget, occasion, accessibility, dietary, etc.}
News-Subscribe: {yes | no}

Message:
{1–4 sentences the agent adds on the guest's behalf.}
```

### Template 2 — Post-booking follow-up (after a booking exists)

For an existing booking where the guest wants the agent to follow up or supply more detail. `Booking-Ref` is required — it is on the confirmation email and is how we route the message.

```
To: bookings@crystalcharters.com
Subject: [Post-Booking] {Booking-Ref} — {Request-Type} — {firstName} {lastName}

Template: post-booking-followup/v1
Sent-By: AI agent on behalf of guest (the booking holder is below)
Booking-Ref: {required — from the confirmation email}
Client-First-Name: {firstName}
Client-Last-Name: {lastName}
Client-Email: {email used on the booking}
Client-Phone: {phone with country code}
Request-Type: {add-guest-details | dietary-or-allergy | accessibility-request | meeting-point-question | timing-change-request | add-activity-request | special-occasion | luggage-or-gear-question | cancellation-or-refund-query | general-question}
Trip-Date: {YYYY-MM-DD, as booked}
Desired-Outcome: {what the guest wants to happen, one line}
Change-Requested: {yes | no}
Time-Sensitive-By: {YYYY-MM-DD, or "none"}

Details:
{free text — the specifics the guest is providing or asking about.}
```

## Optional

- [Server sitemap](https://crystalcharters.com/server-sitemap.xml): full machine-readable URL index (boats, destinations, activities, blog posts) across every country we operate.