WayfareBack to travel assistant

Private partner preview

One integration, three travel views

Reuse the starter's current-flight capabilities while this profile adds visibly synthetic hotel and rewards views. The website never receives the Nuitee or model credential.

  1. Install dependencies

    Installs the pinned website, Assistant SDK, MCP, and test dependencies.

    pnpm install

  2. Start the website

    Opens the guest shell locally. It does not start an assistant session until the first message is submitted.

    pnpm dev:web

  3. Validate the partner MCP

    Validates and smokes the isolated partner profile. The normal starter checks remain separate and credential-free.

    pnpm agent:check:partner

  4. Add the public embed ID

    Set this non-secret deployment coordinate only after an assistant-enabled deployment provides the real public embed ID.

    NEXT_PUBLIC_NOODLE_ASSISTANT_EMBED_ID

Capability boundary

Search → Compare → Verify

Flights use the connected Nuitee provider. Hotels and loyalty are deterministic illustrative data. The experience does not book, hold inventory, redeem points, collect passenger details, take payment, or issue a ticket.

Identity extension

Optional OAuth

Keep the guest path for these travel capabilities. When you add a real identity-bound capability, follow docs/oauth.mdto replace the public embed transport with a backend-authenticated Assistant session exchange.

Repository help

Support

Use the repository's SUPPORT.md policy and sanitized issue forms. Never include credentials, provider bodies, customer data, or private deployment URLs in a report.