How We Built Travel Guild: A Builder’s Honest Account
Summary
Travel Guild is an agentic travel assistant designed to safely transact on a traveler's behalf, addressing the high failure rates (up to ~30%) observed in single-LLM agents attempting complex booking tasks. Initial attempts with a single qwen3-max agent showed unpredictable failures like inventing hotels or silently dropping itinerary legs, even with thorough prompt engineering. The core problem was identified as structural, not algorithmic, stemming from mixing generative reasoning with deterministic constraint enforcement. Travel Guild's architecture employs eleven specialist agents (e.g., Budget, Risk, Visa/Compliance) coordinated by a deterministic orchestrator, each handling a non-overlapping responsibility and gating its boundary with deterministic checks. This "society of specialists" approach, combined with four distinct interaction protocols (MCP, A2A, UCP, AP2), achieved 100% booking success with zero variance on feasible scenarios. The system also incorporates robust safety gates for budget, visa, health, risk advisories, and insurance, culminating in a "one consent" human authorization step.
Key takeaway
For AI Architects designing agentic systems involving real-world transactions, recognize that robust safety and reliability stem from architectural design, not just model capabilities. You should prioritize separating stochastic generative tasks from deterministic constraint enforcement by employing specialist agents and external, unarguable gates. Implement distinct communication protocols for different interaction types, such as dedicated commerce and payment protocols, to ensure verifiable human consent and prevent silent failures or unauthorized spending.
Key insights
Safe autonomous agentic commerce is an architectural problem, not a model problem, requiring structural containment of stochasticity.
Principles
- Separate generative reasoning from deterministic enforcement.
- Contain stochasticity structurally, not algorithmically.
- Use specialist agents for tractable subproblems.
Method
Implement a "society of specialists" architecture where eleven agents handle distinct, gated responsibilities, coordinated by a deterministic orchestrator using four specific interaction protocols (MCP, A2A, UCP, AP2).
In practice
- Design external gates for budget, compliance, and risk.
- Implement distinct protocols for different interaction types.
- Use exact DP for NP-hard subproblems.
Topics
- Agentic AI
- Multi-Agent Systems
- Travel Technology
- AI Safety
- Deterministic Systems
- Commerce Protocols
Code references
Best for: AI Engineer, AI Architect, MLOps Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Towards AI - Medium.