About GoChatTravel
The booking engine behind the API, the storefront and the chat.
What we build
GoChatTravel is a booking engine. Availability, pricing, cart, booking and post-sale across 15+ supplier APIs, deterministic throughout.
Chat is one way onto it, not the product. The same engine is an HTTP API, so it drives ordinary web forms or screens inside your own app just as well. Or take the reference storefront — search, cart, checkout, already built — and put your brand on it.
Language models sit at the edge and do one job: talk to the person. They do not pick the hotel, calculate the price or confirm the booking.
The rule we hold to
"We ship a supplier only when cancelling and refunding are automated. If cancelling requires a phone call, it isn't finished, and we don't sell it."
Leadership
Two co-founders, each with more than twenty years in architecture and backend engineering. High-load distributed systems, and supplier APIs of every generation — modern REST and NDC alongside the legacy GDS and mainframe-era protocols that still carry most of the world’s inventory.
- Alexey Chekhovskiy — co-founder, and the architect of the distribution and commerce side of the engine: GDS and NDC connectivity, hotel APIs, the checkout and payment rails, loyalty and enterprise authentication. Has taken Amadeus API integrations through vendor certification twice and holds Amadeus Level 1–3 agent certification. LinkedIn
- Andriy Nikulytsya — co-founder, and the architect of the processing core: supplier normalisation and aggregation, cart state, and the booking pipeline that turns a cross-supplier cart into confirmed reservations. That is the layer that maps every supplier’s schema into one internal representation, so a single search fans out across every provider and comes back as one ranked list, and connecting a new supplier never touches booking logic. It is the hardest part of the engine and the reason everything above it stays simple. LinkedIn
We have built systems together for more than five years, through the acquisition of one employer by another, before any of this existed. Nothing significant in the engine is designed by one of us alone.
Who we work with
More than 15 supplier APIs — GDS, NDC, bedbanks and direct connections — merged into one normalised result list. Provider-by-provider detail is shared under NDA. Payments run on Stripe, or on the partner’s own rails.