JourneyBay 2.0: An AI Travel Engine That Holds the Entire Trip in One Itinerary

Trip planning used to live across a dozen tabs. The map in one, the hotel booking in your inbox, flight PDFs on your desktop, visa rules on the embassy site, notes in Notion. Everything stayed in your head and kept slipping out.

JourneyBay 2.0 pulls it back into one living itinerary. Not a tab and not a folder, but a single trip plan that updates with you and remembers what you just added or moved.

The 1.0 was an AI assistant that answered in text. The 2.0 is an AI Travel Engine that edits the trip.

What changed in 2.0

The first version of JourneyBay was a decent AI planner. You described a trip, you got an itinerary. Everything after that - moves, search around, booking import, visa checks - stayed manual work.

The 2.0 takes that work off your shoulders. AI now:

• understands the whole trip context: destination, dates, pace, passport, places and bookings you have already added;
• acts on the trip instead of only describing it: adds, moves, deletes, searches around, updates a day;
• works through a set of tools over a single trip model: place search, itinerary edits, activity moves, booking import, visa context, and preparation;
• is available both inside the app and in Claude Desktop, Codex, or Cursor through MCP.

Let’s walk through the features.

A trip from one prompt

Starting a trip in 2.0 is simple. You write a short request and JourneyBay turns it into a ready itinerary.

“Three days in Istanbul, slow mornings, viewpoints, and good food” is enough to get a day-by-day breakdown, a set of places on the map, a first route with distances, and a time of day for each activity. From there you can edit the plan: move activities, search nearby, add bookings.

Same idea as in 1.0, with two important differences.

• AI returns a structured itinerary with tappable places and a real map, instead of a text blob.
• The plan stays alive. Every next message works on top of the existing trip, without regenerating it from scratch.

An AI chat that edits the trip

In a regular AI chat you get advice and then move it into a map, calendar, or notes by hand. In JourneyBay 2.0 the chat is an action interface.

You write “find two sunset spots and dinner fifteen minutes away”. JourneyBay searches, validates, and returns places as cards inside the answer. A card can be opened, inspected, and added to the right day of the trip. The next message remembers what you just added and keeps working around that point.

What the chat can do inside an itinerary:

• search for places by description (“a quiet café with a view”, “a recharge spot”);
• show tappable place cards inside answers;
• move activities between days;
• search around a place you already picked;
• update the schedule of a day;
• factor in passport, pace, and preferences.

The main difference from a classic AI chat is that the answer does not end in text. If you ask to “move the museum to day five”, the itinerary actually updates in the right day instead of returning a new paragraph of advice.

Booking import from PDFs and photos

The most common workaround in any trip is bookings scattered across email. A PDF from an airline, a screenshot of a hotel confirmation, a photo of a train ticket.

In JourneyBay 2.0 it takes one step. You upload a file - PDF, photo, screenshot. The app recognises the booking, pulls out dates, places, flight numbers, and details, and drops it into the right day of the trip.

Supported:

• flights, including multi-segment itineraries;
• hotel and rental bookings;
• train and bus tickets;
• car rentals;
• tours and activities.

If you already have an active trip with overlapping dates, the booking is linked to it automatically. If there is no trip yet, a new one is created with this booking as the first event. Conflicts (a double hotel for the same dates, overlapping flights) are shown before saving.

Worldwide planning

The 1.0 was tilted heavily toward popular destinations from CIS travellers. The 2.0 opens the planner to the whole world.

JourneyBay 2.0 takes into account:

• any citizenship of the user;
• any destination country;
• visa context, where it is available from official sources;
• seasonality and trip pace;
• personal preferences.

Under the hood there is one trip model. It works the same way for a three-day Istanbul and a three-week Bolivia. Itineraries, place search, and booking import are global. Visa context is shown where there is an official source. For rare citizenship-destination pairs the app says plainly that you should check the embassy site.

Visa context from official sources

Visas are an area where any mistake costs a lot. You can be denied boarding. You can be turned back at the border. Any AI aggregator is on thin ice here.

We took a conservative path. Visa context in JourneyBay 2.0:

• comes from official government portals (foreign ministries, immigration services);
• shows the source and the date of the last update;
• is phrased as “according to the official source X”, without claims like “you don’t need a visa”;
• lives next to the preparation checklist beside the trip - which documents tend to matter, the minimum passport validity, what border officers usually ask for.

It is a first reference for preparation, not a substitute for official verification. Critical requirements should still be checked on embassy and consulate sites before the trip.

Preparation next to the itinerary

Preparation used to live separately from the plan. The checklist in one app, documents in another, visa links in browser bookmarks.

In 2.0 everything sits next to the itinerary:

• a personal preparation checklist tied to the destination and dates;
• documents (passport scans, insurance, confirmations) stored beside the trip;
• visa context shown in the same place as the itinerary;
• AI remembers what you have already marked as done.

The checklist is shaped per destination. For Turkey it will be one list (a passport with at least six months of validity, travel insurance, a printed hotel confirmation for border officers). For Japan it will be a different one (a visa application, a bank statement, a return ticket). The list can be edited by hand, and AI flags things people usually forget.

This closes the gap between “build a plan” and “actually be ready for the trip”.

Places that fit the moment

Recommendations in 2.0 are sharper than in 1.0. Each place arrives with an explanation of why it fits this specific moment. Quiet morning, calm sunset, loud evening, walk after lunch.

JourneyBay considers:

• trip pace (slow, normal, active);
• the current day and time;
• places already added nearby;
• personal preferences and saved spots;
• season and time of day.

The idea is less tourist noise and more fit for a real moment. Instead of “top ten restaurants in Istanbul” - “where to have dinner on the evening of day three, when you are tired and want a quiet place near the hotel”.

A concrete example. You added a morning walk in Sultanahmet to the itinerary. You ask AI: “where to have breakfast nearby, no queues and a view”. The answer is a single card with a tag like “opens at 8:00, Bosphorus view, usually empty until 10”. No “best ten breakfasts in Istanbul” - one place for a specific morning.

Bring your own LLM key (BYO LLM)

For people who already live in their own AI stack, the 2.0 ships a separate mode. You plug in your OpenAI, Claude, or Gemini key and use JourneyBay directly with that provider.

What that gives you:

• token spend and rate limits stay with your provider;
• the subscription is cheaper than regular Pro because it does not include tokens;
• you can pick the model;
• spend is visible inside every conversation, so it is clear how much AI used on a specific reply.

It is built for people who already pay OpenAI or Anthropic for their own work and would rather not double-pay through one more AI service.

MCP access for Claude Desktop, Codex, and Cursor

The freshest piece of the release. JourneyBay 2.0 ships with its own MCP server at mcp.journeybay.co. That means Claude Desktop, Codex, Cursor, and other compatible clients can work with your authorised trip data.

The flow looks like this. During a meeting you write inside Claude: “open my April trip and show what I already have booked in Istanbul”. Claude calls JourneyBay through MCP, reads the itinerary, and returns the current list of bookings and activities right inside the chat. You can then ask it to find a place near your hotel or add an activity - Claude prepares the change and you approve it inside the app with one tap.

What that gives you:

• you work with the trip where you already work with AI;
• no manual sync between Claude and the app;
• any change needs confirmation, so AI can’t accidentally rewrite the itinerary without your tap;
• access is OAuth-controlled - you can see what is connected and revoke it any time.

MCP is a power-user feature for now. But this is exactly the direction the product is heading: AI as the operating layer of the trip, available from any AI client the user already lives in.

Who it is for

JourneyBay 2.0 doesn’t try to be for everyone. The main scenarios we built it around:

• Independent travellers planning 2 to 4 trips a year. The full loop: idea → itinerary → bookings → preparation → trip.
• People who outgrew “a list of restaurants in Google Maps”. They want a structured plan with days, activities, and preparation, without hours in Notion.
• Couples and families. Booking import from a partner’s inbox, shared preparation, one itinerary.
• AI power users. People who already live in Claude or Codex and want the trip there through MCP.

If you only need a “top 10 places in this city” generator, JourneyBay 2.0 is overkill. If you want one itinerary for the whole trip, this is for you.

Availability and pricing

JourneyBay 2.0 is available on App Store, Google Play, and RuStore.

Plans:

• Free - basic AI chat, manual planning, up to one active trip.
• Pro - the full AI chat with tools, booking import, visa context, no limit on trips.
• Trip Pass - a one-time payment for two months of Pro, no auto-renewal.
• BYO LLM - Pro with your own OpenAI / Claude / Gemini key.

Free trial - 7 days, cancel any time.

Get JourneyBay 2.0 on App Store, Google Play, or RuStore. To try MCP straight away, see the docs at mcp.journeybay.co.