Elior Farajpur

My first attempt at building a travel planning agent looked exactly like most early prototypes: one big model, a few tools, and a long system prompt. It worked fine until the moment real-world complexity showed up. Flights came from a clean API, hotels lived behind a shifting web UI, and the model kept mixing instructions, forgetting context, or hallucinating steps. That’s when it became obvious: the single agent wasn’t the solution, it was the bottleneck.