Airline commerce
for AI agents.
Let agents complete supported purchases and trip changes through your systems, under your rules. Start with one workflow, with clear permissions, verified outcomes and a path for exceptions.
Open specification (AFCI v1.7)Your endpoint, your dataMaintained workflow operations
Prefer email? nabiha@aviark.co
Illustrative walkthrough
From a trip-change request to a verified result.
Example: a traveler needs to change their flight date. Aviark retrieves options, checks permissions and submits the approved change to the connected backend. This illustration reflects a sandbox workflow with a test backend and simulated event; traveler requests can also initiate it.
Watch an existing trip
The traveler links their account and asks the agent to monitor a specific order. Permission to watch does not authorize a change.
{
"order_id": "ZZ-ORD-2026-8841",
"monitoring": "subscribed",
"execution_permission": "not_granted"
}Halcyon Air (ZZ) is a fictional carrier; fares and policies are illustrative.
Read all five walkthrough steps
Watch an existing trip
The traveler links their account and asks the agent to monitor a specific order. Permission to watch does not authorize a change.
Receive an airline event
An airline signal prompts the agent to retrieve current order state. The event itself is a hint, not an executable quote.
Present a live quote
The endpoint checks eligibility and returns priced options from the connected backend. The agent presents the actual financial impact and any changed conditions.
Collect separate permissions
The traveler approves the selected action on the airline’s review page. Airline policy or an operator separately authorizes it. A new quote requires a new approval.
Execute and verify
The endpoint submits the approved change and records the result. Completed requests replay safely. An uncertain backend outcome stops further execution until reconciliation.
Alongside your existing systems
Close the gap between an API call and a completed task.
Your NDC, PSS and order vendors remain the source of offers and bookings. Aviark adds the agent-facing workflow: connect the request to current options, collect the right permissions, execute and verify the result. Existing vendors may already cover parts of this. Start by validating one gap: can a permitted agent complete a date change, safely handle a retry and stop an uncertain outcome for reconciliation?
Agents need permission to act
A personal agent can find an answer and still lack the identity, current order state and authority required to complete a purchase or change.
Commerce spans fragmented systems
Offers, purchased seats and bags, benefits, payments and order changes can live in different systems. An agent needs a coherent workflow with explicit failure handling.
More traffic needs operating controls
Browser agents and API clients can both create load. Airlines need attributable callers, bounded access and events that reduce repeated status checks.
{
"action": "change_flight",
"order_id": "ZZ-ORD-2026-8841",
"carrier": { "code": "ZZ", "name": "Halcyon Air" },
"new_flight": "ZZ204",
"fare_difference": { "total": 220.00, "currency": "GBP" },
"traveler_consent": "approved_for_selected_option",
"airline_authorization": "granted_by_policy",
"status": "change_confirmed"
}Illustrative outcome, not a live API response. Halcyon Air (ZZ) is fictional.
After booking
Complete the trip the traveler wants.
Beyond the current date-change workflow, the product target is to preserve purchased services and support post-booking purchases. Each added workflow needs its own pricing, permission, fulfillment and exception checks against the airline backend.
Measure fulfilled purchases and incremental contribution, alongside preserved entitlements, resolution cost and repeat contacts. Agree the baseline and supported scope with your team.
Proof of Value metrics agreed with your team
The traveler asks. The agent acts.
Your airline defines the supported choices.
The current sandbox demonstrates a supported flight change. Post-booking purchases, upgrades and service preservation are core implementation priorities; the combined result is not yet complete.
The Platform
Five layers. One governed interface.
A maintained workflow on your airline-controlled endpoint. Your order system remains authoritative; production coverage depends on the selected adapter and validated integration.
Airline Connectors
Adapters connect the selected workflow to available airline APIs. Access and compatibility must be validated for each backend.
Canonical Commerce Schema
Give the agent consistent offers, prices, conditions and current order state.
Policy & Orchestration Engine
Check eligibility and caller identity; keep traveler consent separate from airline authorization and record both.
Agent Interface
An MCP server and REST API on the airline’s own endpoint (agent-api.{airline}.com), built on AFCI v1.7 - an open specification.
Execution Layer
Complete supported purchases and changes, verify order and service outcomes, and recover safely from retries or uncertain execution. Available capabilities depend on the airline adapter.
How to Start
Start with one workflow, one caller class.
A paid Proof of Value with an agreed workflow, access plan and scorecard. Technical discovery determines the scope, timing and path to production.
Assess
Identify a purchase, upgrade or servicing workflow with customer demand and measurable value.
Connect
Confirm order authority, product availability and adapter coverage. A traveler request or an airline event can start the workflow.
Prove
Validate the selected workflow before a limited rollout. Choose the agent channel around demand and integration readiness.
Measure
Measure fulfilled purchases, incremental contribution and servicing cost against a matched baseline, including exceptions.
You retain your customer data, policies and endpoint control. Production agreements define software licensing, ongoing support and transition terms.
Book the demoThe current demo shows a supported change on a sandbox booking. Post-booking ancillary purchases, upgrades and service preservation are core product priorities requiring further implementation.
FAQ
Answers before you ask.
What can Aviark do today?
The sandbox supports search, booking, paid seats at booking, date changes and cancellation using a test backend. Production airline integration needs separate validation. Post-booking ancillary purchases, cabin upgrades and purchased-service preservation remain in implementation.
Why use Aviark if AI agents can already use our website?
A sanctioned endpoint lets your airline identify callers, scope access and manage load. Aviark focuses on completing supported tasks with clear permissions, verified outcomes and safe recovery. Browser agents can still be useful; the endpoint also needs quotas and operating controls.
Will it work with our NDC, PSS and existing vendors?
Compatibility depends on your backend capabilities, access and order authority. We validate one selected workflow and adapter before making a production commitment. Existing vendors may cover parts of the same work, so the evaluation must establish a real capability or operating gap.
How are agent actions authorized, and how is passenger data handled?
For servicing, traveler consent to the exact quoted action and airline authorization are separate; airline policy cannot replace traveler consent. Your airline controls access and data policy. Authorized agents receive information needed for the task, so data flows and platform retention need review. Your order system remains authoritative.
What does a Proof of Value involve, and how long does it take?
A paid Proof of Value starts with one workflow, one caller and an agreed baseline, scorecard and exception path. It validates access, backend behavior and execution controls before a limited rollout is agreed. Plan around 6–10 weeks after required access is available, subject to technical discovery.
How is Aviark priced?
The Proof of Value is paid and scoped during discovery. Implementation is priced separately from annual production operation, which covers agreed supported workflows, capacity and support responsibilities. Added workflows and capacity are priced explicitly; the agreement defines licensing and transition terms.
Evaluating an integration? Our buyer guide covers agent platforms and discovery, ticketing responsibilities, data and compliance, and AFCI licensing.