Has been an interesting few days building an AI powered itinerary generator. The steps seem simple enough, but you have to be SO explicit with the parameters so AI doesn’t fly off the rails. Even then, the output is not always exactly the way you need it to be, which is without any fancy content sentences or “warm and fuzzy” humanizing content – but you only want that type of output in the final generation, the rest needs to remain the same, and collect preferences in a friendly manner.
The steps to create something like this was definitely a fun exercise. It tied directly into our previous AI work with a model backend powered by Nebius.
- Explicitly define the information you’re trying to collect
- Enter the exact JSON structure the AI should follow
- Explicitly stating “itinerary” (singular) to avoid the plural confusion
- Require JSON-only output to prevent inconsistent formatting
- Defining all required fields with data types
- Include optimization constraints clearly
It pulls from a curated database of locations, and needs to be customized to a specific location, but it’s major steps forward in automating the whole experience.
