Have your agent call us “Am I actually going to make this connection?” For a long time, answering...
For nearly a decade, Lumo’s API has helped companies build better ways to predict, understand, and manage travel disruption.
Airlines, TMCs, travel companies, and technology providers have used Lumo’s data and predictions to build dashboards, alerting tools, trip-monitoring systems, and operational workflows.
Lumo's customers have included a wide range of companies – from startups to Fortune 500s using the API from everything from trip planning to monitoring to waiver management.
And that list continues to grow.
From API to MCP
More recently, we introduced the Lumo MCP server. It powers experiences such as our Lumo Concierge product and gives AI applications a more natural way to work with travel intelligence.
Instead of integrating every data source and building every prediction model themselves, an AI agent can ask questions such as:
- What is the risk that this traveler will miss their connection?
- Is there a waiver that applies to this itinerary?
- What will the weather be like at O'Hare tomorrow?
- Where is this flight coming from?
Until now, access to Lumo’s API and MCP server generally meant reaching out to us, having a conversation, working through pricing, provisioning credentials, and setting up a commercial relationship before building could begin.
That worked for larger customers. But it was not the right experience for everyone.
Removing the speed bumps
One thing was becoming increasingly clear: the technology was not the bottleneck. The process was.
Pricing discussions are difficult when a team has not yet had the opportunity to understand the value of the product or how much usage it will require. Volume can be hard to estimate before an application exists. And a process involving calls, contracts, API-key provisioning, usage monitoring, and monthly invoicing can slow down both sides.
Startups are building at an extraordinary pace. We do not want to put unnecessary speed bumps in their way.
Just in the past week, we have heard from:
- A team building an application to help airline pilots get where they need to go
- A company managing hotel staffing based on flight schedules
- An AI-first TMC building disruption management into its core offering
In the old model, each conversation could have led to multiple calls, a free API key, manual usage monitoring, contract negotiations, and monthly invoicing.
That is no longer necessary for standard usage.
Developers can now sign up, create API and MCP credentials, and start building. The standard self-serve tier covers the first $20 of monthly usage, so teams can test the product without an upfront commitment. Usage is pay-as-you-go, billed by credit card, and volume discounts scale automatically as usage grows.
That means teams can start with a small experiment and continue building without having to come back and renegotiate when their application takes off.
Simple pricing. Fast access. A process built for how modern software gets created.
What can you build with Lumo?
Lumo provides more than raw data. We add predictive and operational intelligence that helps applications answer questions before a disruption becomes obvious.
Capabilities include:
- Flight disruption predictions
- Missed-connection likelihood estimates
- Airport disruption forecasts
- Terminal and airport traffic-management predictions
- Airport arrival-rate forecasts and capacity constraints
- Weather and airport-condition context
- Airline waiver search and applicability checks
- Flight, trip, and inbound-aircraft information
- Webhooks for monitoring trips and receiving updates when conditions change
These capabilities can be accessed through the REST API or the MCP server, depending on what you are building.
Put disruption intelligence inside the experience
A travel company could use Lumo to build a conversational experience where a traveler asks:
I am on flight AB1234 tomorrow. What does my airport look like, and what is the risk of delay?
An airline operations analyst could ask:
What is my expected A60 performance at ORD tomorrow?
A travel agent or traveler could ask:
Is there a waiver that applies to AB1234?
Those questions require more than a flight-status lookup. They require context, prediction, and the ability to connect information across flights, airports, weather, capacity, operational constraints, and airline policies.
That is the layer Lumo provides.
Developers should not have to become aviation experts—or build an entire disruption-intelligence operation—to add these capabilities to their products.
They can use the REST API to build predictable, structured integrations. They can use the MCP server to give AI agents access to travel intelligence through natural-language questions and tool calls. They can use both together when that is the right architecture.
Start building
Lumo’s API and MCP server have been used in production by companies across the travel industry. The self-serve launch makes the same capabilities available to teams that want to move quickly, test an idea, and scale when they find product-market fit.
🚀 Go to thinklumo.com/api-mcp to explore the documentation, pricing, and signup process.
Start small. Build quickly. Add better disruption intelligence to the travel experiences people already use.
