Trip feasibility checker
Will your itinerary survive the trip?
Plans that look fine on paper fall apart on the day: a museum closed on Tuesdays, a 20-minute transfer squeezed into 10. This checks every stop against real data, shows you the evidence, and suggests fixes it has already re-checked.

Six checks, each with its source
Opening hours
A visit falls outside a place’s hours, or the place no longer exists.
OpenStreetMap
Public holidays
A day is a public holiday that may close or crowd what you planned.
Nager.Date
Travel time
The gap between two stops is shorter than the trip there, plus a buffer.
OSRM routing
Daily load
A day is longer, busier or more walking than your pace allows.
Your preferences
Hotel red flags
Reviews repeatedly mention noise, dirt, safety or a poor location.
Booking.com reviews (Kaggle)
Closures
A place is shut for works or keeps special hours on your dates, as its website or the web says.
Web search, sources linked
How it works
- 1
Paste
An itinerary from a chatbot or your own notes, with the city and start date.
- 2
Confirm
Check the stops it read from your text and fix any it got wrong.
- 3
Repair
See each problem with its evidence, and fixes that passed every check again.
An AI model reads your text and proposes fixes. The checks themselves are code working on real data, and a fix is only shown once every check has run again on the changed plan.