Is Ancilair affiliated with DragonPass or LoungeKey?

No affiliation is claimed here. Those brands are widely known lounge-access networks travellers and cards already recognise. An agent platform may route across multiple lounge suppliers under contract; always read the live served-by field and supplier terms.

What inputs does a lounge API need from an agent?

Typically airport code, terminal when known, date/time window or stay hours, and sometimes passenger count or access type. Strict validation should reject incomplete calls before they hit a supplier.

How do lounges differ from airline-included access?

Ticketed airline lounges and status benefits are not the same product as third-party day passes. Agents should not promise airline lounge entry from a third-party search result.

Blog

Airport lounge API for AI agents: search and book by terminal

By Loris Mazloum Published 6 October 2026

Long connections are where AI travel agents either feel magical or useless. Airport lounge access is a concrete, bookable job: find a lounge near the right terminal, show the price, issue a pass after confirmation.

This article is for builders adding a lounge booking API (or routed lounge search) to agents and OTAs. Public Ads volume for “airport lounge booking” is small; traveller demand inside trip chats is not.

Tool shape

Routed search keeps the agent’s schema stable while suppliers change:

anc.lounge.search {
  airport: "CDG",
  terminal: "2E",
  date: "2026-10-14",
  stay_hours: 4
}

Illustrative response fields: an offer list, which supplier answered, the quoted cost, latency, and cache state. Booking tools then take an offer id with an idempotency key.

Networks travellers already know (adjacency, not affiliation)

Consumers often recognise lounge networks and card benefits (for example DragonPass- or LoungeKey-branded access, airline alliances, or bank programmes). Agent platforms sit one layer up:

You integrate APIs / contracts, not a consumer app.
You must name the supplier that answered a routed call.
You must not imply Ancilair (or your agent) is those networks, or that a day-pass equals elite airline lounge rights.

Positioning gap vs consumer apps: agents need machine schemas, prepaid metering, and the same auth as eSIM and fast track—not another white-label webview.

Pairing lounges with the rest of the layover

A practical playbook:

Detect a long layover from the PNR.
anc.lounge.search at the connecting terminal.
If security sits between gates, consider fasttrack.book.
esim.plans for the destination country.
Present one bundle; book only on explicit yes.

MCP walkthrough: Travel MCP server for ancillaries.

Implementation notes

Prefer terminal-aware search; airport-only results frustrate users at large hubs.
Pin a contracted lounge supplier for resellers who already wholesale a network.
Cache identical searches carefully—inventory and day-pass prices move.
Show the price the supplier quotes. Do not put a stand-in price in the product.

Sources

Ancilair — routed anc.lounge.search example on the shelf

Not a partnership announcement. Lounge access rules and participating locations change; verify per supplier.

Questions

Is Ancilair affiliated with DragonPass or LoungeKey?: No affiliation is claimed here. Those brands are widely known lounge-access networks travellers and cards already recognise. An agent platform may route across multiple lounge suppliers under contract; always read the live served-by field and supplier terms.
What inputs does a lounge API need from an agent?: Typically airport code, terminal when known, date/time window or stay hours, and sometimes passenger count or access type. Strict validation should reject incomplete calls before they hit a supplier.
How do lounges differ from airline-included access?: Ticketed airline lounges and status benefits are not the same product as third-party day passes. Agents should not promise airline lounge entry from a third-party search result.