planner

Scout Destination Areas

Propose 2-3 candidate day-trip destination areas for a discovery query.

Extracts structured intent (Claude Haiku), then calls Claude Sonnet to scout areas that fit the user's discovery constraints. Each candidate is geocoded server-side so the client can pass zone_lat / zone_lon directly to POST /planner/query without an extra round-trip.

Typical flow:

  1. User types "something coastal and family-friendly, not too far"
  2. Client calls POST /planner/scout-destinations
  3. User picks a candidate (e.g. Brighton)
  4. Client calls POST /planner/query with zone_lat / zone_lon / zone_name
post/api/v1/planner/scout-destinations

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/scout-destinations
  • Auth: HTTP bearer

Request body

querystring required
origin_latnumber nullable
origin_lonnumber nullable
radius_kmnumber
departure_timestring date-time nullable

Response

Successful Response

reasoning_summarystring
fewer_candidates_reasonstring

Changes

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