Give it a start, an end and a date. It builds the itinerary from the distances we publish, then writes it up. Every figure is labelled with where it came from.
Most AI trip planners ask a language model what it remembers about a place. That is how you end up with a bus that does not run and a hotel that closed in 2019.
This one works the other way round. The itinerary is built first, in your browser, from the same distance and drive-time figures published on this site's route guides. Only once the plan exists is the language model asked to write it up, and it is given those figures as the only ones it is allowed to use. It cannot introduce a distance, a fare or a property name of its own.
That matters here more than it would elsewhere. This site is built to be quoted accurately by search engines and AI assistants, and a planner that contradicted our own guides would undo that. So the model writes. It does not know.
Every leg in a generated plan carries a label.
From our own data means the figure is published on one of our route guides, or comes from a named government source such as the Nainital district administration. The plan shows which. These cover Haldwani, Kathgodam, Nainital, Bhimtal, Sat Tal, Bhowali, Kainchi Dham, Mukteshwar, Almora, Ranikhet, Kaladhungi, Ramnagar for Jim Corbett, and Pantnagar.
Approximate means we do not publish a guide for that stretch. Garhwal, the Chardham temples, Rishikesh, Haridwar, Mussoorie and the long approach drives from Delhi, Lucknow or Chandigarh all fall here. The planner gives a range rather than a false decimal, says the figure is unchecked, and tells you to confirm it locally. We would rather show you the seam than hide it.
It will not invent a hotel. Accommodation only ever comes from the properties we actually list, all of which are in Haldwani and Kathgodam. If your route does not pass through, it says we do not list there rather than making something up.
It will not quote a bus time, a train number, a permit rule or a ticket price, because we have not verified those and a wrong one strands somebody.
It will not ask for your name, phone number or email, and it refuses to send them onward if you type them into the notes box. The plan is generated from place names and a date. Nothing else is needed and nothing else is sent.
It is at its best on the trip this site knows: arriving at Kathgodam by train, basing on the plains where rooms cost the same in June as in November, and day-tripping into the hills. That is the shape of most Kumaon journeys and it is the one we have measured.
It is thinner the further west you go. A Chardham circuit will produce a usable skeleton with honest ranges, but it will not be better than a Garhwal specialist. We would rather say that than pretend otherwise.
Haldwani and Kathgodam sit on the plains where the train arrives, where the dawn cab is easy to arrange, and where rooms cost the same in June as in November.
Yes. There is no sign-up, no account and no charge. It runs on free service tiers, which means it has a daily ceiling. If it has been used heavily that day the write-up may be unavailable, and the page will say so and still show you the itinerary, the distances, the hotel matches and the guide links.
From the route guides published on this site, and in a few cases from the Nainital district administration. Each leg in a plan shows its source. Haldwani to Kainchi Dham is 49 km via Bhowali on NH 109, Haldwani to Nainital is 38 km via Kaladhungi, Haldwani to Bhimtal is 31 km, Haldwani to Almora is 87 km. Those are our published figures and the planner uses exactly them.
It is not given the opportunity. The itinerary is computed before the model is called, and the model receives those numbers as the only ones it may use. It writes the prose around a plan that is already fixed. If the writing service is unavailable, the plan itself is unaffected.
It will plan them, but honestly rather than confidently. We publish guides for Kumaon, not Garhwal, so those legs are marked approximate, given as ranges, and flagged as unchecked against our own reporting. Use them as a skeleton and confirm the detail locally.
Because those are the only properties we list. All 25 are in Haldwani and Kathgodam. Rather than pad the plan with places we have never looked at, the planner recommends from what we actually cover and says nothing where we cover nothing.
No. The plan is built in your browser and the itinerary is sent to the writing service only to be turned into prose. We do not ask for or store contact details. If you use the share button, the plan is encoded into the link itself rather than saved on a server.
No, and deliberately. The plan is rendered on the page without changing the address, so no new URL is created for a search engine to find. This page is indexed. The itineraries it produces are not.