Frequently Asked Questions

Voyager is an AI-powered travel planning agent. You describe your trip — destination, dates, budget, and preferences — and the agent searches real APIs for flights, hotels, and experiences to assemble a complete, budget-aware itinerary. You can then iterate conversationally to refine the plan.

Voyager uses a multi-step tool-use loop powered by Claude. When you describe a trip, the agent reasons about your requirements and calls real APIs 3-8 times per turn — searching flights, comparing hotels, finding experiences, and tracking your budget between each step. Unlike simple chatbots, the agent makes decisions based on the results it gets back, just like a human travel advisor would.

Flight and hotel data comes from live Google Flights and Google Hotels results, fetched via SerpApi at the moment you search. Experience and restaurant recommendations come from the Google Places API. Every price you see is a real, searchable result, not a language-model guess.

Prices are pulled from live APIs at the time of your search and reflect real availability. However, travel prices change frequently — a price shown during planning may shift by the time you book. Voyager is a planning tool, not a booking engine. We always recommend verifying the final price when you book through the airline or hotel directly.

Not yet. Voyager is currently a planning and itinerary tool. It helps you find the best options within your budget and organizes them into a day-by-day plan. Booking integration is on our roadmap.

Voyager is a portfolio demo. It is free to use, there is no paid tier, and there is no intent to monetize it as a commercial product. Every API call the agent makes (Anthropic, SerpApi, Google Places) is paid for by the author as a technical demonstration.

Voyager does not make money. It is a technical demonstration of an agentic AI travel planning pattern, built as a portfolio piece. There is no business model, no subscription, no affiliate commission, and no advertising. The per-trip cost structure is analyzed honestly in the published Criticism audit.

No. Voyager has no partnerships, no affiliate links, and no pay-for-placement deals. The agent optimizes purely for your stated preferences and budget. What you see is what the APIs return, filtered by your criteria.

We store your account information (email, name), your saved trips and itineraries, and conversation history so you can pick up where you left off. We cache API responses briefly to improve performance but do not store raw travel search data long-term.

Your data is never sold. We send search queries to SerpApi (which aggregates Google Flights and Google Hotels) and to the Google Places API to fulfill your requests. Those queries contain trip parameters (dates, destinations) but not your personal identity. Conversations are processed by Anthropic's Claude API under their data usage policies.

Yes. You can delete your account at any time from the Account page. This permanently removes all your trips, conversations, and personal data from our systems within 30 days.

Voyager is powered by Anthropic's Claude, using the tool-use API. The agent has access to structured tools for searching flights, hotels, experiences, calculating budgets, and looking up destination information. It decides which tools to call and in what order based on your request.

Traditional chatbots generate a single text response. Voyager uses an agentic loop: the AI receives your message, decides to call a tool (like searching flights), reads the result, reasons about it, then decides the next action. This loop continues until the agent has enough information to present a complete plan. A single turn may involve 3-8 tool calls with reasoning between each one.

The agent is limited to 15 tool calls per turn as a safety measure. In practice, most trip plans require 4-8 calls. If you need more detail, you can ask follow-up questions and the agent will make additional searches.

If a data source is temporarily unavailable, the agent will let you know which part of the search couldn't be completed and offer to try again. It won't fabricate data — if it can't reach the flight API, it will say so rather than making up prices.