UJ Boats Group API — shipped + ready for the design layer

Field inventory — 110-field schema, scored on 117 records

Knowing what's safe to design around versus what shows up rarely changes how the UI behaves. The Boat detail page already does this — every section is conditional on data presence so we don't render "Beam: undefined".

API contract — the surface Jaime designs against

Three endpoints. All return JSON. All cached at the edge. All safe to call from anywhere on the same origin (and from elsewhere by enabling CORS if needed later).

Boat shape (normalized — lean projection of the 110-field raw)

{
  documentId: string,              // primary identifier
  yachtWorldId: string?,
  stockNumber: string?,
  status: "Active" | "sale pending" | ...,
  saleClass: "New" | "Used",
  title: string,                   // ListingTitle or "year make model"
  year: number?, make: string, model: string,
  boatName: string?,               // e.g. "Wine Down"
  category: string?,               // "Power" (all current)
  classes: string[],               // e.g. ["Bowrider", "Ski and Wakeboard"]
  hull: { material?, id? },        // material, HIN
  price: {                         // null if PriceHideInd=true
    display: string,               // raw "36000.00 USD"
    numeric: number,               // 36000
    original?, hidden: boolean
  } | null,
  length: { nominal?, overall?, beam?, meters? },
  engines: { count, hours?, power?, drive? },
  location: { city?, state? },     // actual boat slip (not office)
  rep: { name?, email?, phone? },
  description: { primary?, legalNotice? },     // HTML strings
  media: {
    primaryImage?: string,
    images: [{ url, caption? }],
    hasVideo: boolean, has360: boolean, hasImmersiveTour: boolean,
    embeddedVideos: [{ url, title?, thumbnail? }]
  },
  coOp: boolean,
  externalLinks: [{ url, text, type }],
  meta: { itemReceivedDate?, lastModified? },
  raw: { /* full upstream record — escape hatch */ }
}

Defined in src/lib/boats-api.ts. The raw field is an escape hatch — anything not yet projected is reachable.

Open follow-ups — what's NOT done yet

• Write-API mapping (1-day spike). Find the upstream method= values (create/update/delete). Crawl4ai timed out on api.boats.com/docs earlier — re-try with a longer wait, or just ask Jason Smith for the docs PDF.
• Launch + production secret binding. When Jaime's design lands and we promote to launch, I have to wrangler secret put BOATS_COM_UJ_KEY --env launch before the first launch deploy. Same for production at cutover. Documented in the deploy notes; won't forget.
• HTML sanitization. The description.primary field is HTML from BoatWizard. XSS surface is low (UJ staff don't have motive) but I want DOMPurify (or rehype-sanitize) on the server side before public launch. Tracked.
• Email obfuscation. Currently the sales-rep email + phone show as plain text on the detail page (matches what Boats Group already exposes publicly). Confirm with you whether we proxy it through a Worker form to fight scrapers, or leave it (UJ may want the white-glove "call our team" signal).
• SEO depth. Detail pages get OG image (primary boat photo) and meta description (first 200 chars of description). JSON-LD Product schema is next — boats.com may have a Google rich-result advantage UJ doesn't because the syndication strips it.
• Image lazy-loading already on; image optimization not yet. Boats Group's CDN serves 2MB XLARGE images. Pages Worker can pipe through @astrojs/cloudflare's Image binding (already configured) for resize + WebP — cuts page weight ~70%. Phase 2.
• Filter UX. Currently a basic GET-submit form. Once Jaime's design is in, this becomes a left-rail facet panel with brand + length + price + location + new/used.