Paste an itinerary from anywhere, whether an LLM wrote it or a booking site, and TripCheck checks the whole trip together against the mistakes that cost travelers money: missed connections, hotel nights that do not line up with the flights, short passports, missing visas or travel authorizations, and rental cars booked before you land.
ReadyThe validator is called when you click Validate trip.
1. Drop the itinerary
or try a sample:
2. Review the trip
Reading free text is a best effort. Check every field before you validate. The validator only sees what is in these fields.
Rental car (optional)
Scope of this validator
TripCheck: round-trip itineraries for a US-passport traveler with up to two outbound and two return flights, one hotel and an optional rental car. It checks the trip as a whole, not each booking alone.
Any case, not just these samples. The validator handles any itinerary built from the flights, hotels and countries in its catalog, in any combination, including combinations no sample here shows.
What it checks
Connections: same airport, and enough minutes to connect, outbound and on the way home
The return flight leaves from where the trip ends and after the outbound arrives
The hotel is in the arrival city, with nights matching arrival and departure, including red-eye flights
Length of stay against the visitor limit for US citizens
Passport validity beyond departure where the country requires it
Visa or e-visa and electronic travel authorization recorded where required
Rental car pickup after landing and return before departure
Not in this validator today
Non-US passports
One-way and multi-city trips, or more than one hotel
Live flight schedules, prices or availability (the catalog is a fixed illustrative set of 8 countries, 25 flights and 9 hotels)
Baggage, seat, fare-rule or insurance checks
Health entry requirements, and transit visas beyond the entries recorded
Want more, such as other passports or more airports and hotels? Tell Predictika and we will extend it.
Notes for the engineering team
What this page does. It sends one request to the validator’s validate endpoint: {session_id, choices:[{parapath,value}…, {parapath:"_sys", value:["EOS"]}]}. It carries no trip rules. Every verdict and message comes back from the engine.
No health check. The page makes no call on load. The first request is the one sent when you click Validate trip, and the status bar at the top reflects the result of the latest call. The Validate button is enabled as soon as the required fields are filled.
Auth. Every request carries one fixed header, X-API-KEY, with a value hardcoded in the CONFIG block. Anyone who opens this page can read it from the source, so treat it as a non-secret key.
CORS. Browsers can call the endpoint only if it allows this page’s origin. Tested October 8, 2026: the page ran from the same server as the validator, so the browser made no cross-origin call. A separate preflight check showed the server allowing the requesting origin and the X-API-KEY header, so a copy hosted on another site should also work.
Sessions. Each validation uses a fresh session_id. Call 2 of the protocol (Execute = True) is not used; this page only validates.
Catalog. The dropdowns list the catalog’s keys (Flights.csv, Hotels.csv, Countries.csv). If the catalog changes, update the CATALOG object.