The AI engine for travel management.
Aviare is the autonomous booking, servicing, and IRROPS layer TMCs and OTAs run on. Your agents stop being a call center and start being a code base — book, reprice, rebook, refund, settle, report. At machine speed. Within your policy. On your inventory.
What Aviare replaces
The expensive parts of running a TMC.
Routine bookings
Agent-handled searches, fares, holds, and ticketing. Aviare does them autonomously, 24/7, with no queue.
IRROPS desks
Schedule changes, cancellations, denied boardings — handled by the agent layer in seconds, not by a 3 AM page to a human.
Exchange and refund ops
Fare-rule reading, EMD handling, BSP settlement — coded as typed agents, not as agent training docs.
After-hours coverage
No human staffing for nights, weekends, or holidays. Aviare runs the same way at 3 AM as at noon.
What it does
The full booking lifecycle, end to end.
Autonomous booking pipeline
Search → price → book → ticket → exchange → refund → settle. Coordinated by Tarmac, executed by Otaip/Haip agents. No human-in-the-loop unless you want one.
Proactive disruption monitoring
Every active reservation is watched. Schedule changes, IRROPS, irregular ops — detected and resolved against your policy before the traveler files a ticket.
Policy + compliance enforced in code
Corporate policy, fare rules, ATPCO Cat 1–33, EU261 / US DOT, BSP/ARC settlement — all encoded as typed contract gates, not as prompts.
Your inventory, your channels
Plug your existing supplier contracts — Sabre, Amadeus, Duffel, Navitaire, NDC, direct carriers, Hotelbeds. Your margins stay yours.
Built on the only auditable travel-AI stack in the world.
Otaip (Apache 2.0) handles air. Haip (Apache 2.0) handles hotel. Tarmac is the travel-tuned LLM that routes intent. Every decision Aviare makes is logged, typed, and reviewable. If compliance asks why a $4,000 fare was booked, your CFO can trace it end to end — not because we built a dashboard, but because the underlying agents are open source code your team can read on GitHub.
Why TMCs choose Aviare
The economics change.
Cost per booking collapses
The marginal cost of an Aviare booking is compute, not a head. Volume scales without staffing.
Margin moves where it should
You stop paying labor to do what software can do. Your supplier contracts, your markup, your policy stay yours.
You operate around the clock
No after-hours desk. No weekend skeleton crew. No premium pay for IRROPS coverage.
Compliance is auditable, not promised
Every booking is traceable through the Otaip contract pipeline. Six deterministic gates between LLM intent and execution. Hallucinations get caught at the schema layer, not in your customer's inbox.
Open core, not vendor lock
Otaip and Haip are Apache 2.0. The code your operation runs on is on GitHub. If we go away, you don't lose your stack.
No pricing page. Just a conversation.
Aviare is sold to TMCs and OTAs that want their booking operation to run autonomously. Tell us your supplier mix and your current per-booking cost. We'll show you what changes.