planner

Nl Query

Natural-language planner endpoint.

Accepts a free-text query and returns 1-2 structured itinerary plans. The response is persisted so the user can retrieve their history and submit feedback on individual plans.

Steps (inside NLPlannerService.plan):

  1. Claude Haiku extracts structured intent from the query
  2. User's library places are haversine-filtered; weather fetched concurrently
  3. Google Places gap-fills types with fewer than 2 library results
  4. Claude Sonnet generates a single coherent day plan (returned as a one-item list for API backward compatibility)

Raises: 422 if Claude Haiku cannot parse the query into structured intent 500 if Claude Sonnet cannot produce a valid plan

post/api/v1/planner/query

Request

  • Base URL: https://yondry.app (the document declares no server; this is the origin it was published from)
  • URL: https://yondry.app/api/v1/planner/query
  • Auth: HTTP bearer

Request body

querystring required
origin_latnumber nullable
origin_lonnumber nullable
radius_kmnumber
departure_timestring date-time nullable
travel_modestring
optimize_for_returnboolean
vibesstring[]
companionstring
prefer_discoveryboolean
discovery_weightnumber nullable
zone_latnumber nullable
zone_lonnumber nullable
zone_namestring nullable
previous_plan_idstring uuid nullable
follow_up_querystring nullable
timezonestring nullable
languagestring
campaign_slugstring nullable
anchor_place_idstring nullable

Response

Successful Response

generated_plan_idstring uuid required
querystring required
weatherstring nullable required
generated_atstring date-time required
plans_usedinteger nullable
plans_limitinteger nullable

Changes

No recorded changes to this operation across all 1 revision of this API.