Skip to main content

Trip Planner

@keeb/trip-plannerv2026.11.01.1· 19d agoBEHAVIORS
01README

Trip-planner services with canned data, for workshops and demos: extract (structured trip requirements from a plain-English request, standing in for a Claude Haiku call), search_flights (priced flight options, standing in for Google Flights) and search_hotels (AI-rated hotels under a nightly cap, standing in for hotelist.com). Same arguments and resource shapes as @adam/trip-planner and @keeb/hotelist, so an itinerary behavior and a plan-trip workflow built on these run with no API keys and no network. The data is fixed: a comfortable 10-day April trip from SFO to Tokyo on a $4,000 budget, three flights and four hotels. Built for the Behavior-Centric AI Design workshop.

02Behaviors1
@keeb/trip-plannerv2026.11.01.1trip_planner.ts
fn extract(request: string)
Return structured trip requirements (always the same canned SFO-Tokyo trip; the request is recorded, not parsed).
ArgumentTypeDescription
requeststring
fn search_flights(departureIds: string, arrivalIds: string, outboundDate: string, returnDate?: string, adults?: number, cabin?: string)
Return priced flight options (always the same three canned SFO-Tokyo flights; arguments are validated, not used).
ArgumentTypeDescription
departureIdsstring
arrivalIdsstring
outboundDatestring
returnDate?string
adults?number
cabin?string
fn search_hotels(city: string, max_price_usd?: number, sort?: string)
Return AI-rated hotels (always the same four canned Tokyo hotels; arguments are validated, not used).
ArgumentTypeDescription
citystring
max_price_usd?number
sort?string

Resources

requirements(infinite)— Trip requirements from a request (canned; stands in for Claude Haiku extract).
flights(infinite)— Priced flight options for a route (canned; stands in for Google Flights).
search(infinite)— AI-rated hotels in a city under a nightly cap (canned; stands in for hotelist.com).
03Stats
B
75 / 100
Downloads
23
Archive size
7.4 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented0/1missing
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License1/2partial

    no SPDX license declared

  • Verified public repository0/2missing
04Platforms
05Labels