Available now

Make catalogue-aware travel decisions before inventory search.

MyEscapePlan turns natural-language or structured travel intent into ranked options within the destinations, products and suppliers your business chooses to sell, then optionally verifies the shortlist against live inventory.
Your catalogue and supplier policy define the decision boundary. MyEscapePlan does not replace inventory providers or booking systems.
Discovery itself is planner-only and makes no live supplier calls. Provider-backed Verified Search is a separate optional workflow for pilots that need it.
Built for websites, AI assistants, travel platforms and partner channels that need consistent, explainable travel decisions before downstream supplier search.
Read API documentation
From London, 4 days next month, under £300pp, somewhere warm with direct flights.
Example catalogue-aware decision plan
1
Málaga
3–5 days · flexible window
Strong fit
2
Alicante
3–4 days · flexible window
Strong fit
3
Palma
3–5 days · verify fare first
Possible fit
€3,395 saved
up to per month on flight search alone²
Illustrative upper bound on the stated 1,000,000 logical flight-shopping-unit basis: 1,000,000 × 67.9% × €0.005. Treat this as an illustrative upper bound, not an observed customer saving; confirm provider billing and your own traffic before forecasting.
67.7% less
shopping space across flight and accommodation discovery¹
67.9% on Flights and 67.5% on Accommodation; mean 67.7% across equal-sized tracks, while retaining mean 67.5% Recall@10.
679,000 fewer
logical flight units per 1,000,000 shopping units¹
1,000,000 × 67.9% = 679,000 logical flight units avoided. On accommodation, 1,000,000 × 67.5% = 675,000.
Why the engine, not a bigger model

Reduction is the consequence. These are the causes.

A frontier model can understand the request. Making large-scale travel ranking fast, reproducible and grounded requires a decision and data layer around it. That is the layer we have built, and the shopping-space figures below are what falls out of it.
Speed

Hundreds of destination-date options, ranked in seconds.

The expensive reasoning is precomputed into an immutable snapshot, so a request scores a large candidate set against the traveller's constraints in one pass instead of resolving destinations one lookup at a time. Planning returns inside a hard latency budget rather than degrading into a long agent loop.
Reproducibility

Same request, same data version, same ranking.

Ranking is deterministic scoring over versioned data, not generation. A model reads the traveller's sentence; it does not choose the answer. Results change when the snapshot changes and not otherwise, which is what makes them auditable, cacheable, and testable against a fixed benchmark.
World model

Breadth without one lookup per destination.

Typical conditions by month, seasonality, airport reachability from an origin, points of interest and cost proxies are resolved ahead of the request across tens of thousands of destinations. Widening the candidate set costs compute, not a network round trip or a model call per destination, so lesser-known destinations compete on merit instead of being excluded by a curated shortlist.
Learned signals

Verified outcomes improve future rankings.

Which routes are actually served from an origin, which destinations come in on budget in a given month, which candidates verify successfully and which travellers pursue are carried as signals per destination and month, and are rebuilt into each published snapshot. This is proprietary outcome history that a frontier model does not have unless it is given it.
Constraint integrity

Hard constraints stay hard. Relaxation is explicit.

Budget, dates, duration, origin and party are compiled into a typed contract that records which are binding and which are preferences. Soft constraints are widened only under explicit policy, hard ones are not, and any relaxation is reported back with the result rather than silently absorbed.
Explainability

Every candidate carries why it is there.

Scores decompose into independent signals — intent match, seasonal fit, reachability, experience fit and affordability — so a downstream product can show a reason, a support team can audit a result, and a regression is attributable to a component rather than to a prompt.
What changes

What MyEscapePlan unlocks.

The same monthly volume, shopped differently. The benchmark uses a stated basis of 1,000,000 logical flight-shopping units; provider savings must be modeled from billable counts in your own traffic.

Today

Destination and date selection
Every plausible destination, date window and trip length is a candidate for a supplier call.
Rounds before a shortlist exists
Several: query, read results, adjust constraints, query again.
Logical flight-shopping units per month

1,000,000

MyEscapePlan
Discovery + Verified Search

Unlocked

Destination and date selection
Ranked candidates only, chosen against the traveller's stated constraints.
Rounds before a shortlist exists
One request returns the shortlist, with reasons and qualitative fit.
Logical flight-shopping units per month

321,000

The traveller gets what they asked for: options that fit, at prices confirmed against live inventory, with less time spent searching.
Independent industry evidence

Travel shopping already runs at volumes where the wrong request is expensive.

Look-to-book ratios put many shopping requests behind every booking, and agentic travel adds another source of iterative, automated search as AI travel agents explore and refine options on a traveller's behalf.
1,000–10,000+:1
OTA & metasearch look-to-book
IATA's 2019 scalability study measured shopping requests per booking for OTA and metasearch traffic, the highest-volume shopping channel it examined.
IATA NDC Scalability Study · 2019 ↗
100–300:1
Airline-direct look-to-book
IATA's 2019 scalability study contrasted OTA and metasearch volumes with roughly 100–300 shopping requests per booking on airlines' own websites.
IATA NDC Scalability Study · 2019 ↗
150+
Tool calls in long-horizon agentic travel
TRIP-Bench reports realistic long-horizon travel dialogues that can involve more than 150 tool calls across 18 travel tools.
TRIP-Bench · 2026 ↗
Look-to-book is an industry shopping-to-booking ratio. It is not a claim that a single traveller request produces that many HTTP calls. TRIP-Bench separately reports 150+ tool calls in realistic long-horizon travel dialogues; those calls span travel tools and are not flight-supplier calls alone.
Measured with MyEscapePlan

A smaller shopping space that still holds the right options.

Canonical benchmark · Flights + Accommodation · 4 scenario families · 40 requests · September 2026
67.7%
Mean logical shopping-space reduction
Across the equally sized Flights and Accommodation tracks.
67.5%
Recall@10 retained
Mean across the equally sized Flights and Accommodation tracks.
67.8%
NDCG@10 ranking quality
Mean across the equally sized Flights and Accommodation tracks.
What the reduction is worth

A smaller shopping space compounds at look-to-book volumes.

Because look-to-book puts many shopping requests behind every booking, a reduction of this order compounds across every request a platform makes rather than saving once.
1,000,000 × 67.9% = 679,000 logical flight units avoided. On accommodation, 1,000,000 × 67.5% = 675,000.
Illustrative upper bound on the stated 1,000,000 logical flight-shopping-unit basis: 1,000,000 × 67.9% × €0.005. Treat this as an illustrative upper bound, not an observed customer saving; confirm provider billing and your own traffic before forecasting.
Gross provider savings = (billable searches before − billable searches after) × contracted marginal provider cost. Net savings also subtract MyEscapePlan, infrastructure and integration costs.
Potential net savings = gross provider savings − MyEscapePlan, infrastructure and integration costs.
What the API does

Four capabilities, applied before any supplier call.

Destination candidate generation

Resolve open-ended intent against a managed destination universe while preserving hard traveller constraints.

Intelligent date and duration selection

Reason across flexible windows and trip lengths to prioritise useful combinations instead of forcing one brittle interpretation or shopping every possibility.

Ranked shopping candidates

Prune, rank and explain the combinations worth live verification, with controlled relaxation when exact options fail.

Known-commitment trip anchoring

Plan around caller-known commitments at the supplied destination, with full date coverage by default or any shared local date when requested.
Search-space intelligence

Not every plausible date deserves a supplier call.

A flexible request can imply hundreds of destination, date and duration combinations. MyEscapePlan narrows that space first, prioritising combinations using traveller constraints, flexibility, affordability signals and candidate fit.
Why now · Agentic travel

We expect agentic travel to multiply shopping volume.

As agentic travel matures, AI travel agents can branch across destinations, dates, durations, airports, budgets and follow-up refinements from a single user request — then re-check the most promising options. Every branch can create downstream flight, hotel or package shopping work.
IATA's 2025 Look-to-Book work explicitly highlights Generative and Agentic AI when discussing rising search volumes and offer creation. MyEscapePlan is designed to sit before expensive live inventory APIs and decide which branches are worth shopping.
01

One traveller request

A human can ask broadly: somewhere warm, four days next month, under budget, preferably direct.
02

An agent explores many branches

Agentic travel planning can autonomously test destinations, dates, durations, airports and revised constraints instead of waiting for manual clicks.
03

Discovery narrows live shopping

MyEscapePlan ranks and prunes candidate combinations first, so downstream flight-shopping APIs receive the small set most worth verifying.
Benchmarking principle
Recent travel-agent benchmarks such as TREK treat tool efficiency as a first-class evaluation dimension alongside task correctness. MyEscapePlan applies the same principle to shopping: preserve the good options while reducing unnecessary downstream work.
Read TREK ↗
Why this layer exists

Supplier APIs answer “what inventory exists?” They do not decide the entire travel search strategy.

Discovery requires intelligent selection across destinations, dates and durations, plus affordability reasoning, candidate pruning and fallback rules before high-cost live shopping begins.
Natural-language intent parsing
Caller-supplied trip anchors for known external commitments
Managed destination universe and customer-provided destination allowlists
Intelligent date-window and duration selection
Affordability signals
Candidate pruning and ranking
Fallback and relaxation logic
Planner-only discovery with no live supplier calls
Optional provider-backed Verified Search as a separate workflow
Reasons and qualitative fit for downstream UX
Best-fit customers

For teams building travel products, not another inventory source.

AI-native travel

Trip-planning startups, conversational travel assistants, itinerary builders and travel-agent copilots.

Existing travel platforms

OTAs, metasearch, package-holiday companies, flight-search products and publishers adding discovery.

Agent and LLM platforms

General AI products that need travel discovery capability without rebuilding travel-specific planning infrastructure.
Discovery API Pilot

4–6 week integration pilot

API access, a generous fixed usage allowance, integration support, basic usage analytics and enough real traffic to evaluate recommendation quality and shopping-space reduction.
Sources
1. MyEscapePlan Discovery benchmark, September 2026: logical shopping-space reduction and Recall@10 by track.2. Nuitee Connect API pricing, verified 2 September 2026: flight-search surcharge €0.005 per request when the applicable search-to-booking threshold is exceeded.
The headline is an illustrative upper bound based on stated logical shopping units, not observed customer savings. Confirm the provider's billing rule, booking ratio, contract and currency before treating it as a forecast. Volumes above are a stated basis, not observed customer traffic.

MyEscapePlan Business

AI travel decisioning for travel businesses: connect customer intent with your catalogue, supplier policy and commercial rules across digital and advisor workflows.
MYESCAPEPLAN LTD · Company no. 16395758 · Registered in United Kingdom
Discovery API and Advisor are available now. Tour operator and Meetings & Events workflows can be piloted around the same controlled decisioning layer.
Discovery benchmark figures, their formula and their limitations are published in full.
Read the benchmark methodology ↗
Tour operator and Advisor pilots can start with your existing catalogue and supplier policy.