tasi-travel

To generate a travel itinerary with evidence-backed recommendations, provide your destination, dates, traveler count, budget, and preferences. The system uses browser-first Ctrip extraction to source hotels, flights, and POIs, preserving source URLs for citations while labeling estimated values.

You can create route maps for a daily travel schedule by requesting Amap route links during itinerary generation. The system renders driving or walking route previews for each day, automatically respecting via-point and point-count limits.

Travel planning handles missing or degraded hotel and flight data through a provider routing policy with graceful fallback. If browser-first Ctrip retrieval is blocked or returns poor results, it automatically switches to alternative providers to maintain data quality.

Constraint-driven trip planning requires YAML-defined inputs including destination, date range, traveler count, and budget. You can also include optional preferences like must-visit locations, places to avoid, hotel choices, and transportation methods.

Itinerary generation verifies budget and time logic through a consistency verification pass. It checks time logic, commute load, and activity fit, while outputting a detailed budget breakdown for transportation, hotels, and dining.

Values in your generated itinerary are labeled as uncertain when data quality degrades or specific details are inferred rather than directly sourced. The system explicitly labels these estimated values to distinguish them from provider-backed, cited recommendations.