We got tired of planning
trips in 47 tabs.

The idea for Mezin showed up on a rainy weekend in 2025. The plan was simple: ten days in Portugal, two travelers, shoulder season, mid-range budget, enough flexibility to swap a beach day for a wine day. By Saturday afternoon, the desk looked like the wreckage of a small bureaucracy. Twelve hotel tabs. Four flight engines. A spreadsheet for the day-by-day. A photo of a Lisbon tram map pulled from a Reddit thread. Two different opinions about whether Évora was worth the detour. And a creeping, slightly insulting feeling that this is exactly the work a computer was supposed to be good at.

The product that should have existed didn't. So we made one.

Booking aggregators are not on your side. The default sort is “our picks,” which is a polite name for “the listings that pay us the most.” The filters are powerful enough to feel useful and shallow enough to keep you scrolling. And the prices you see are the same prices the hotel will quote you directly, because the commission comes out of the supplier's margin, not your wallet — a detail nobody mentions because mentioning it makes the whole sorting choice harder to justify.

Itinerary builders have the opposite problem. They're built by people who haven't been there, padded with what the SEO tool said to include, and they collapse the moment your trip doesn't fit the template. A general-purpose chatbot will cheerfully invent a hotel that closed in 2019 and a tram line that doesn't exist, because the loss function rewards a confident answer over a correct one.

None of these are calibrated to you, with your dates, your budget, and yourtolerance for an early flight on the way home. So planning a trip becomes a meta-task: assembling the answer yourself from sources that don't talk to each other.

A single conversation that ends with a real trip — itinerary, hotels, transit, tours, restaurants, ready to book — built around your constraints and grounded in availability that exists at the moment Mez tells you about it.

Not a booking engine pretending to be a friend. A friend who happens to have access to booking engines.

The four rules that govern what Mez surfaces and how we run the business:

1. The ranking is blind to commission.When Mez chooses between two hotels, the model does not see what either partner pays us. Fit, fit, fit — then real availability and price. We've made this an explicit, auditable rule because it's the single biggest thing that distinguishes us from the rest of the booking web. See the affiliate disclosure for the long version.
2. We disclose the affiliate relationship everywhere it's relevant. Footer, blog posts, inside the chat. No buried link, no “sponsored” labels in 9-point gray.
3. We test what we recommend.Editorial pieces on the blog are written from places we've actually been. When that's not possible for a destination, we say so explicitly and lean on primary sources rather than regurgitated listicles.
4. If we don't know, we say so.The model is instructed to prefer a flagged uncertainty over a confident guess. “I'm not sure this place is still open — confirm before booking” beats inventing a phone number.

Under the hood, Mez is a language model wrapped in retrieval — the way most good AI products work now — but a lot of the value is in what we don't let it do.

• Live pricing and inventory.When Mez suggests a hotel, the price and availability are pulled from the partner's API at request time, not from training data. If the room sells out between Mez showing it and you clicking, that gap is the partner's booking flow — same as any other booking site.
• No hallucinated availability. Mez can only recommend hotels, tours, and restaurants that resolve to a verified record at recommendation time. The model is forbidden from inventing names; if a query returns no results, Mez says so rather than fabricating an option.
• Grounded in your constraints.The whole conversation — dates, budget, party size, style — is kept in the context window. When Mez recommends a $380 hotel for a $200/night budget, that's a bug, not a feature. We treat it as one and fix it.
• Hand-off, not man-in-the-middle.Mezin doesn't take payment, hold reservations, or wrap the partner's checkout. When you book, you book directly with Booking.com (or GetYourGuide, or Viator, or whoever) under their terms, with their customer support, and their cancellation policies.

Mezin is built and operated by {{OPERATOR_NAME}}, working solo from {{OPERATOR_LOCATION}}. Background: a long career split between software and spending too much time on the road. The character of the product — wry, opinionated, anti-spam, slightly anti-corporate — is a deliberate choice. If it feels like the opposite of an OTA, that's on purpose.

There's no growth team. There's no investor pressure to surface what pays most. There is one person who would rather ship a smaller product that earns trust than a bigger one that doesn't.

We read everything. Bug reports, hotel recommendations Mez should have known about, feature requests, complaints about a recommendation that didn't work, polite disagreements about the role of AI in travel — all welcome.

hello@mezin.ai is the inbox. Press goes to press@mezin.ai. If it's urgent, say so in the subject line; otherwise we usually answer within two business days.