DEV Community: Becky_dev

The Next Travel Search Engine Might Be a Conversation. The Hard Part Is What Happens Next

Becky_dev — Wed, 28 Oct 2026 12:21:20 +0000

Meta Muse, Agoda, and the infrastructure challenge behind the next generation of AI travel agents.

The next time someone plans a vacation, they might not open a travel website.

They might simply ask an AI assistant:

“I want to spend four days in Tokyo with my partner. Somewhere quiet, close to great food, easy to get around, and under $200 a night. Can you find something that actually fits?”

No endless tabs. No repetitive filters. No comparing the same hotel across five platforms.

Just a conversation.

But here is the question that matters more to travel developers than the conversation itself:

Once an AI understands what a traveler wants, can it connect that intent to a real, available hotel at a price the traveler can actually book?

That is where the next phase of AI travel gets interesting.

1. Travel Discovery Is Moving Into the AI Conversation

On October 28, 2026, Agoda announced that it had become an active connector in Meta's personal AI agent, Muse, in Singapore. The integration allows users to discover destinations, book hotels, and manage itineraries through a conversational interface. Agoda is also available through Muse in Japan. Source: Agoda's announcement.

This is more than another AI feature launch.

It points toward a possible shift in how travelers discover and access travel services.

Traditional travel search starts with a destination, dates, filters, and a list of results. Conversational AI starts with intent.

A traveler might not know which neighborhood to choose, what hotel category suits their trip, or how much convenience is worth paying for. They may simply describe the experience they want.

An AI agent can translate that context into a more useful search.

And when travel services become accessible through connectors, the assistant can potentially move beyond general advice and interact with actual travel inventory.

The important distinction is that AI discovery and AI execution are two different problems.

Generating a convincing hotel recommendation is one thing. Finding a room that matches the request, checking current rates, and connecting the traveler to a valid booking option is another.

The second problem is where infrastructure starts to matter.

2. The Real Bottleneck Isn't Intelligence. It's Access.

AI models are getting better at understanding natural language, reasoning about preferences, and planning multi-step tasks.

But a model cannot reliably recommend a bookable room using outdated prices or incomplete inventory.

Consider a simple request:

Find me a four-star hotel in Osaka, within walking distance of a train station, for two adults next weekend, under $150 per night.

To answer usefully, a travel agent needs more than general knowledge about Osaka.

It needs to resolve several practical questions:

Which hotels match the location and budget?
Are rooms available for the requested dates?
What are the current rates and relevant room conditions?
Are taxes, fees, and cancellation policies clear?
Where can the traveler continue to book the selected option?

Each step depends on access to travel data and services that can respond to the actual request.

Without that connection, an AI assistant risks producing an answer that sounds useful but cannot support the next action.

This is the infrastructure gap in AI-powered travel.

The challenge isn't simply to make models smarter. It's to connect them to reliable, structured, and sufficiently current information.

A hotel recommendation is only as useful as the data and booking path behind it.

3. Why MCP Matters for AI Travel Developers

This is where the Model Context Protocol (MCP) becomes relevant.

MCP provides a standardized way for compatible AI applications to discover and interact with external tools and data sources. Rather than building every integration as a completely separate, bespoke connection, developers can expose useful capabilities through an MCP server.

For travel applications, that creates an opportunity to make hotel search and related functions accessible within AI workflows.

Imagine an agent that can:

Interpret a traveler's natural-language request.
Search hotel inventory using the traveler's dates, location, and budget.
Compare available options and relevant hotel details.
Present rates and choices that match the request.
Provide a direct path to the booking process.

The model handles the conversation and reasoning. Connected travel services provide the data and capabilities needed to make the result actionable.

Of course, MCP alone does not guarantee accurate inventory, valid prices, or successful bookings. Those depend on the underlying service, data freshness, error handling, and booking workflow.

That is precisely why the quality of the connection matters.

For developers building AI travel agents, the question is no longer just, “Which model should I use?”

It is also, “Which travel capabilities can my agent access, and how reliably can it use them?”

4. Building the Connection Between AI and Real Hotel Options

At RollingGo, this is the problem we focus on.

RollingGo Hotel MCP connects compatible AI agents and development environments with hotel search capabilities covering more than 2 million hotels across 200+ countries and regions.

The goal is straightforward: make hotel discovery more accessible to AI applications without requiring every developer to build an entire hotel search integration from scratch.

With RollingGo Hotel MCP, developers can work toward experiences that connect natural-language requests with:

Global hotel search and relevant property details.
Real-time room-rate information returned by the service.
Hotel options that can be compared against traveler preferences.
Booking links that help travelers continue to the reservation process.

This distinction is important. Hotel discovery, availability information, and booking execution are related, but they are not identical. An agent needs to present useful options and provide a clear booking path; the actual reservation depends on the relevant booking service and its requirements.

For developers, this means less time spent reinventing basic travel connectivity and more room to focus on the user experience.

For travelers, it opens the possibility of planning a trip through a more natural interface.

For businesses, it creates another way to make travel services accessible within AI-powered products.

Explore RollingGo Hotel MCP: https://mcp.rollinggo.cn/

5. The Next Travel Interface May Not Look Like a Travel Interface

Think about how people use software today.

They open a search engine to research, a travel platform to compare hotels, a map to understand locations, and a booking page to make a reservation.

Each step requires the traveler to switch contexts and translate their original intent into another interface.

AI agents could gradually reduce that friction.

A traveler might describe the whole trip in one place, refine their preferences through conversation, review hotel options, and follow a booking link without manually repeating the same requirements across multiple tools.

This doesn't mean traditional travel websites will disappear. Travelers will still need transparent pricing, clear policies, trustworthy information, and control over purchase decisions.

It means the entry point could become less important than the capabilities behind it.

The interface might be a chat window, a voice assistant, a social platform, or an application that combines several services.

The underlying requirements remain familiar:

Reliable data. Relevant choices. Clear prices. A working path to purchase.

For travel developers, this creates an opportunity to build services that work across multiple AI environments rather than depending entirely on a single front end.

The future may not belong exclusively to the platform with the most attractive interface. It may also reward the infrastructure that makes those interfaces useful.

6. What Developers Should Build for Next

The emerging opportunity isn't simply to add an AI chatbot to an existing travel product.

It is to design travel capabilities that an agent can use reliably.

Here are three areas worth paying attention to.

Make travel data actionable

A paragraph describing a hotel is not equivalent to structured information about location, rates, room options, and availability.

Agents need information they can interpret, compare, and use in subsequent steps.

Design for changing information

Hotel prices and availability can change. A result that was valid when first retrieved may no longer be valid when the traveler is ready to book.

Developers should consider when to refresh information, how to communicate uncertainty, and what happens when a selected option is no longer available.

Keep the path to booking clear

A good travel agent should not stop at a persuasive recommendation.

It should help users understand their options and move toward a real reservation with appropriate pricing information, relevant policies, and a clear next step.

Automation should reduce friction, not hide important decisions from travelers.

These principles matter regardless of which AI assistant, model, or interface ultimately wins the user's attention.

7. From AI That Talks About Travel to AI That Helps Make It Happen

The Agoda–Meta Muse integration is a useful signal of where travel discovery may be heading.

Travel services are beginning to appear within conversational AI experiences, giving users new ways to explore destinations and access existing travel offerings.

But the more interesting development lies beyond the interface.

As more AI agents enter travel, the industry will need better ways to connect natural-language intent with reliable hotel information and real booking options.

That is the layer developers should be watching.

At RollingGo, we believe hotel connectivity should help make AI travel experiences more practical, accessible, and useful across compatible agent environments.

Our focus is not just on helping an AI talk about hotels. It is on connecting that conversation to hotel options, current rate information, and booking links that travelers can act on.

Because the best travel AI experience won't be the one that produces the most impressive answer.

It will be the one that helps someone go from “I want to take a trip” to a useful, bookable option with less friction.

The next travel search engine might be a conversation. The infrastructure behind that conversation will determine how far it can go.

Build with RollingGo Hotel MCP

Building an AI travel agent, hotel discovery workflow, or travel application?

Explore RollingGo Hotel MCP and connect your AI workflow to global hotel search capabilities.

Website: https://mcp.rollinggo.ai/

Developer portal: https://global.rollinggo.store/

AITravel #TravelTech #AIAgents #MCP #AgenticAI #HotelTech #TravelDevelopers

The Next Hotel Search Box May Not Look Like a Search Box: How RollingGo Hotel MCP Connects AI to Real Travel Supply

Becky_dev — Tue, 27 Oct 2026 10:21:50 +0000

AI travel is moving beyond recommendations. The next challenge is connecting natural-language conversations to real hotel inventory, current prices, and bookable options.

1. Hotel Discovery Is Moving Beyond Traditional Search

For years, travelers have followed a familiar path: open a travel website, enter a destination, select dates, compare hotel listings, and move to a booking page.

That journey is beginning to change.

Instead of navigating multiple websites, travelers can increasingly describe what they need in natural language:

“Find me a beachfront hotel in Barcelona for three nights, under $200 per night, with flexible cancellation.”

An AI agent can interpret the request, identify relevant options, and help narrow down the choices. In the future, the search box itself may become less visible, replaced by a conversation that understands the traveler’s preferences and takes action on their behalf.

But a better conversation does not automatically create a better booking experience.

The real challenge is what happens after the AI understands the request.

Can it access useful hotel options? Can it retrieve current rates and availability? Can it provide a reliable path from discovery to reservation?

These questions are becoming central to the next phase of AI in travel.

2. Cloudbeds and Meta Muse Highlight a Bigger Industry Shift

On October 20, 2026, Cloudbeds announced a planned integration with Muse, Meta’s personal AI agent.

According to the announcement, participating hotels are intended to become discoverable through Muse with live rates and availability, while bookings would be completed through the hotels’ own Cloudbeds Booking Engine. The US rollout is scheduled to begin in Q1 2027.

The announcement points to an important development: AI interfaces are becoming potential distribution channels for travel businesses.

For hotels, this could create another way to reach travelers without relying entirely on traditional search and online travel agency platforms. For travelers, it could make hotel discovery feel more natural and less fragmented.

Most importantly, the integration illustrates that AI-powered discovery needs a connection to real hotel supply.

A recommendation generated from general knowledge is not the same as a hotel option that can actually be booked for the requested dates. Travel decisions depend on details that change constantly: room availability, prices, property policies, location, and booking conditions.

Without reliable access to these details, even a highly capable AI agent can struggle to turn a promising recommendation into a useful travel decision.

The next stage of AI travel, therefore, is not simply about making models better at conversation. It is about connecting intelligence with operational data and transaction pathways.

Source: Cloudbeds’ announcement on its planned Meta Muse integration.

3. The Missing Layer Between AI Conversations and Hotel Inventory

A traveler may express a hotel request in one sentence. Behind that sentence, however, several technical steps need to happen.

The AI application must interpret the destination, dates, budget, and preferences. It then needs to query a travel supply source, retrieve relevant hotel information, compare available options, and present results in a format the traveler can understand.

If the traveler decides to proceed, the experience needs a clear booking path.

This is where integration infrastructure matters.

AI applications need structured ways to interact with external tools and services. In travel, those connections help bridge the gap between a model that understands a request and a system that can return useful, actionable information.

The Model Context Protocol (MCP) offers one approach to making tools and data sources accessible to compatible AI applications through a standardized interface.

For travel developers, this creates an opportunity to build experiences around natural-language requests rather than requiring every application to develop an entirely separate integration from scratch.

The goal is straightforward: reduce the distance between what a traveler asks and what an AI application can actually do.

4. RollingGo Hotel MCP: Connecting AI to Real Hotel Search

This is the problem RollingGo Hotel MCP is designed to address.

RollingGo provides an MCP-powered travel supply connection that enables compatible AI applications to access hotel search capabilities through a tool-based integration.

Its hotel inventory covers 2M+ hotels across 200+ countries and regions, giving developers a broad foundation for building AI-powered travel experiences.

Rather than stopping at general travel advice, an integrated application can use RollingGo Hotel MCP to support practical hotel-search workflows, including:

Natural-language hotel discovery: Turn a traveler's request into a hotel search based on destination, dates, budget, and preferences.
Hotel information retrieval: Present relevant property details to help travelers compare their options.
Price and availability queries: Access supported rate and availability information to make search results more useful for real decisions.
Booking links: Provide a path for travelers to continue from hotel discovery to booking.

These capabilities help developers focus on the experience they want to build, while RollingGo provides the hotel-search connection behind it.

For example, imagine an AI travel assistant receiving this request:

“I’m visiting Tokyo next weekend. Find a centrally located hotel near public transportation, with a budget of $150 per night.”

The assistant can use a compatible hotel-search integration to retrieve relevant options, organize the results around the traveler's requirements, and present hotel details and booking links.

The experience becomes more than a list of plausible suggestions. It becomes a workflow grounded in travel supply.

RollingGo Hotel MCP is also available as an official tool in Qwen Work, and developers can explore custom integrations with other compatible AI platforms.

For teams building travel agents, itinerary assistants, or AI-powered travel products, this offers a practical way to bring hotel search into the application they are already developing.

Learn more: RollingGo Hotel MCP

5. From Hotel Search to Agentic Commerce

Hotel search is only one part of the opportunity.

As AI agents become more capable, travel workflows may increasingly combine multiple steps: understanding a trip request, searching for accommodation, comparing options, checking relevant details, and helping the traveler move toward a reservation.

This is part of the broader shift toward agentic commerce, where AI applications do more than suggest products or services. They help users progress through decision-making and purchasing workflows.

Travel is a particularly interesting area for this evolution because it involves multiple suppliers, changing inventory, detailed preferences, and transactions that often require confirmation.

That complexity also makes dependable integrations essential.

A useful travel agent needs access to relevant supply, clear information, and an appropriate way to hand the user off to a booking flow. The exact transaction process depends on the capabilities and authorization of the connected systems.

This is why the infrastructure behind an AI travel experience matters just as much as the interface.

A conversational interface may attract attention. A reliable connection to travel supply is what helps make the experience useful.

6. Why Travel Developers Should Think About Connectivity Now

For developers and product teams, the emerging opportunity is not limited to building another AI chatbot that recommends destinations.

It is about creating applications that can connect user intent with real services.

A few questions are worth considering when designing an AI-powered travel product:

Can the application retrieve actionable information?

Travel recommendations become more useful when they can be grounded in hotel details, prices, availability, and other relevant data.

Can the integration fit the existing development workflow?

Standardized tool interfaces can reduce integration friction and make it easier to experiment with new AI experiences.

Can the user move naturally from discovery to booking?

Search results should support a clear next step instead of leaving travelers to restart the process elsewhere.

Can the experience scale across destinations?

Broad hotel coverage gives developers more flexibility when building products for different markets and traveler needs.

These are not problems that a language model alone can solve. They require a connection between AI capabilities and travel infrastructure.

7. The Future of Hotel Search Is About What Happens Next

The next hotel search box may not look like a search box at all. It may be a conversation inside an AI assistant, a recommendation within a productivity tool, or a travel agent embedded in an application people already use.

But whatever the interface looks like, the underlying requirements remain practical: relevant hotel options, useful information, current rates and availability where supported, and a clear route to booking.

Cloudbeds’ planned integration with Meta Muse is one signal that the hotel industry is exploring how to connect AI-powered discovery with real booking systems.

RollingGo Hotel MCP approaches the opportunity from the travel-supply side, helping compatible AI applications access hotel search capabilities through an MCP-powered integration.

As AI travel develops, the competitive advantage will not come from conversation alone. It will come from connecting that conversation to services that travelers can actually use.

RollingGo is building for that connection: from natural-language hotel requests to useful search results and booking pathways.

Less searching. More useful travel decisions.

Learn more about RollingGo Hotel MCP: https://global.rollinggo.store/

Tags: AI, TravelTech, MCP, AIAgents, HotelTech, AgenticAI, Travel, DeveloperTools

The Next Travel Revolution Won't Happen Inside Another Booking App

Becky_dev — Mon, 26 Oct 2026 10:09:30 +0000

For more than a decade, online travel has been organized around a familiar destination: the booking platform.

Travelers open an app or website, search for a hotel, compare prices, select a room, and complete the reservation. Even when the interface changes, the basic journey remains the same. The traveler goes to the platform.

AI agents introduce a different possibility.

Instead of beginning with a booking website, a traveler might start with a conversation: “I’m attending a conference in Berlin next month. Find me a hotel close to the venue, keep the total cost within budget, and prioritize flexible cancellation.”

The agent becomes the starting point. It interprets the request, accesses relevant services, compares the available options, and helps the traveler decide what to do next.

That shift raises a question for travel technology companies: if the interface becomes more conversational, what infrastructure will make the experience work?

RollingGo is building for this change through hotel search and booking capabilities designed for AI applications.

The interface is changing — but the underlying work remains

The recent expansion of AI travel experiences suggests that discovery and booking are beginning to converge in new ways.

In October 2026, Skift reported that Wyndham Hotels & Resorts was opening its inventory to AI booking assistants, with rates and availability supplied through its central reservation system. The report highlights a practical issue: an AI assistant needs access to hotel systems if it is going to do more than recommend properties.

Read the report: Wyndham Courts AI Booking Agents in Push for Direct Bookings.

The development does not mean traditional booking platforms will vanish. It does show why travel companies are exploring ways to make their services accessible through AI-led interactions.

A new interface does not remove the need for inventory, pricing, reservation rules, and fulfillment. It changes how users reach those capabilities.

This distinction is central to understanding agentic commerce.

What is agentic commerce in travel?

Agentic commerce refers to shopping or service transactions in which AI agents help users discover, compare, and potentially act on available options.

In travel, that could mean an agent helping a user find a hotel, evaluate trade-offs, and move toward a reservation without requiring the user to manually repeat the same information across several websites.

But agentic commerce is not a single capability. It is a series of connected steps.

The agent needs to understand what the user wants. It needs access to reliable information. It must compare options against the request. It needs a way to present the results and, where supported, connect the user to a transaction.

Each step creates a potential point of failure.

If the hotel data is outdated, the recommendation may be wrong. If the booking pathway is unclear, the user may have to restart the process. If the system does not explain cancellation conditions or total costs, the user may make a decision without understanding the trade-offs.

Agentic commerce works best when the intelligence layer and the transaction layer are connected, but their responsibilities remain clear.

Why travel needs an infrastructure layer for AI

Travel is a particularly demanding use case for AI agents because the information is both detailed and time-sensitive.

A hotel is not simply a name and a location. A useful booking decision may depend on dates, room type, occupancy, taxes, cancellation terms, location, amenities, and current availability.

A language model can help interpret preferences, but it should not be expected to invent the operational data required to complete a booking.

That information has to come from connected services.

This is where the Model Context Protocol (MCP) becomes relevant. MCP offers a standardized approach for compatible AI applications to connect to external tools. In travel, a hotel MCP integration can make supported search and booking functions accessible to an agent.

Instead of requiring the AI product to recreate every hotel workflow inside its own interface, the product can connect to services that expose those capabilities.

The agent can focus on the traveler’s intent. The integration provides access to the travel functions it needs.

RollingGo: connecting AI agents with hotel capabilities

RollingGo is developing travel infrastructure for AI-powered products, with RollingGo Hotel MCP focused on hotel search and booking capabilities.

According to RollingGo's published product information, its hotel coverage includes more than two million properties across over 200 countries and regions. The integration is designed to provide compatible AI applications with hotel search, property information, real-time rate information, and booking links or pathways.

That creates a practical foundation for travel products built around natural-language interaction.

Consider a traveler planning a work trip to London. Instead of navigating several separate search forms, the traveler could explain the trip requirements in one conversation. An AI assistant could then use connected hotel capabilities to retrieve relevant options and organize them around the user’s priorities.

The user might care most about the commute to a meeting, while another traveler might prioritize the nightly rate or flexible cancellation. The AI experience can help compare those trade-offs in context.

RollingGo does not need to own the entire customer interface to be relevant to this journey. Its role is to make hotel capabilities accessible to AI applications that want to build useful travel experiences.

That is an important distinction in an ecosystem where the user interface, AI reasoning, travel data, and booking process may be provided by different services.

From a single booking funnel to connected services

Traditional booking platforms often bundle discovery, comparison, reservation, and other parts of the journey into a single destination.

AI-led experiences make it possible to separate those functions.

The traveler may interact with an AI assistant. The assistant may use a hotel-search integration. A booking pathway may connect the user to a reservation service. Additional systems may handle payment, confirmation, changes, and customer support.

This modular structure can make it easier to create new user experiences, but it also makes coordination more important.

Developers need to know what each component can do, what information it returns, and where its responsibilities end. Travelers need to understand whether an option has merely been recommended, whether a rate has been checked, and whether a reservation is actually confirmed.

The goal should not be to hide the entire transaction behind a conversational interface. It should be to reduce unnecessary work while making the important details easier to understand.

What travel startups and developers can build

An AI-friendly hotel integration can support products that look very different from conventional booking websites.

A destination assistant could combine local recommendations with hotel options that match the traveler's dates and budget.

A corporate travel assistant could help employees identify accommodation that meets internal spending limits and location requirements.

An event-planning agent could help attendees find hotels near a conference venue and organize options for different budgets.

A personalized travel planner could use a conversation to gather preferences, then present a shortlist of hotels that fits the itinerary.

A general-purpose AI agent could treat hotel search as one step within a larger task, alongside calendar planning and trip research.

Each use case has different requirements. Some may only need discovery and booking links. Others may need deeper integration with internal policies or reservation management. The right implementation depends on the intended workflow.

RollingGo Hotel MCP provides a way to explore the hotel layer of these experiences without making a traditional booking interface the only entry point.

Developers can review the RollingGo website and the RollingGo Hotel MCP GitHub repository for product information and integration resources.

The business question: who owns the experience?

As AI interfaces become more capable, travel businesses will need to consider where they create value.

Some will focus on customer-facing experiences. Others will specialize in inventory, data, payments, reservation operations, or tools that connect those functions to AI agents.

These roles can coexist. An AI assistant still needs reliable services behind the conversation, while travel suppliers still need ways to make their inventory discoverable and bookable.

The competitive landscape may become more layered, rather than simply replacing one type of company with another.

For users, the important measure is whether the experience helps them find a suitable option with less friction and more clarity. For developers, it is whether the underlying services can support the workflow reliably.

RollingGo is positioning its hotel MCP offering around this infrastructure opportunity.

What must happen before agentic travel becomes dependable?

There are still meaningful challenges.

First, the data must be useful and current. Hotel availability and rates can change quickly, so systems need to handle changing results appropriately.

Second, the booking process must be transparent. Users should see the applicable conditions and know when they are leaving an AI assistant for a separate booking flow.

Third, permissions and user control matter. An agent should not treat every request for a recommendation as permission to make a purchase.

Fourth, developers need clear error handling. A failed search, missing result, or expired rate should produce an understandable response rather than a fabricated answer.

Finally, the experience needs to support the full context of travel decisions. The lowest rate is not always the best option, and a convenient recommendation should explain its trade-offs.

These are implementation challenges, not reasons to dismiss the direction of travel. They show why infrastructure is as important as the AI model itself.

The next booking interface may be a conversation

The travel industry does not need to choose between AI and every existing booking platform overnight. Travelers will continue to use multiple channels, and different use cases will demand different experiences.

But AI agents are creating another route from travel intent to hotel discovery.

For that route to be useful, agents need access to actual hotel information and clear booking pathways. That is the problem RollingGo Hotel MCP is designed to help solve.

The future of travel may include more conversational interfaces, more specialized agents, and more connected services behind them. The critical question is whether those systems can translate a request into an informed, actionable choice.

RollingGo is building for that layer of the transition: helping AI applications connect hotel search and booking capabilities to the moments when travelers need them.

Explore RollingGo Hotel MCP: https://github.com/RollingGo-AI/RollingGo-Hotel-MCP-Global

RollingGo #AgenticCommerce #AITravel #TravelTech #MCP #HotelBooking #AIAgents

From NVIDIA RTX Spark to AI Travel Agents: Why Real-World Data Matters More Than Ever

Becky_dev — Fri, 23 Oct 2026 10:09:51 +0000

How local AI, Model Context Protocol (MCP), and RollingGo Hotel MCP are shaping the next generation of intelligent travel

NVIDIA’s latest RTX Spark PCs signal an important shift in personal computing: AI agents are moving closer to the devices people use every day. But as AI becomes more capable of reasoning, planning, and executing tasks, a new question emerges: What does an AI agent need to move beyond generating answers and start completing real-world tasks?

In travel, the answer involves more than a powerful model. An AI travel agent needs access to reliable hotel inventory, current prices, room availability, booking rules, and tools that connect recommendations to real transactions.

This is where the combination of local AI, Model Context Protocol (MCP), and travel infrastructure becomes particularly interesting.

For developers building the next generation of AI-powered travel products, RollingGo Hotel MCP offers a practical way to connect AI agents with hotel search and booking capabilities across more than 2 million hotels in over 200 countries.

Let’s explore why this matters and how developers can put it to work.

1. NVIDIA RTX Spark and the Rise of Personal AI Agents

On October 16, 2026, NVIDIA announced the availability of its RTX Spark PCs, bringing its Blackwell RTX architecture and AI computing platform to a new generation of Windows computers.

According to NVIDIA’s official announcement, RTX Spark offers up to 128GB of unified memory and up to one petaflop of FP4 AI performance, enabling developers and users to run demanding AI models and agents locally.

The significance goes beyond hardware specifications.

For years, many AI experiences have centered on a simple interaction: users enter a prompt, and a model generates a response. AI agents introduce a different paradigm. They can work toward a goal, choose tools, process information, and coordinate multiple steps to accomplish a task.

Local AI computing can make certain workflows more accessible on personal devices, while also giving developers more flexibility over where inference happens and how their applications are deployed.

However, computing power alone does not give an agent access to every service it might need.

A local model can help plan an itinerary, but it does not automatically have access to live hotel inventory. It can recommend a hotel, but that does not mean it can confirm a room at the quoted price.

Intelligence helps an agent decide what to do. Connected tools help it act on that decision.

That distinction is particularly important in travel, where information changes constantly and users expect recommendations to translate into practical outcomes.

2. Why AI Travel Agents Need More Than a Language Model

Imagine asking an AI assistant:

Find me a four-star hotel in Tokyo for two people next weekend, close to public transportation, with free cancellation and a budget of $200 per night.

A language model can understand the request, identify relevant constraints, and explain what makes a hotel suitable. Yet a genuinely useful travel agent must do considerably more.

It needs to:

Interpret the destination, dates, number of guests, and budget.
Search actual hotel inventory rather than rely on information learned during training.
Compare available properties, room types, prices, and cancellation policies.
Check whether a suitable room is available for the requested dates.
Verify pricing and booking conditions before a transaction.
Help the user proceed through the booking workflow.

Each step introduces a different requirement.

Hotel availability changes. Prices can fluctuate. Cancellation policies differ by room and rate plan. A property that appears suitable in an old article may no longer offer the same conditions.

For these reasons, an AI travel agent needs a connection to live travel services, not just a larger knowledge base.

This is the difference between an AI that talks about travel and an AI that can help users complete travel tasks.

It also explains why travel infrastructure is becoming an important part of the agent ecosystem.

3. What Is MCP, and Why Does It Matter for AI Agents?

The Model Context Protocol (MCP) is an open protocol that standardizes how AI applications connect to external tools and data sources.

Rather than building a separate custom integration for every AI application, developers can use MCP-compatible servers to expose capabilities in a structured way. An MCP client can discover and invoke supported tools, subject to the server's implementation and the application's permissions.

For AI travel products, this creates a useful architectural opportunity.

An agent can use one component to understand a user's request, another to retrieve relevant hotel information, and additional tools to support price verification or other booking operations where those capabilities are available.

A simplified workflow looks like this:

User request → AI agent → MCP client → Hotel service → Structured results → Agent response

The agent remains responsible for reasoning about the user's preferences and deciding which available tools to use. The connected service provides the operational capabilities and data.

MCP does not make an AI model inherently more intelligent, nor does it guarantee that every connected service supports every transaction. Instead, it provides a standardized way to connect supported capabilities to AI applications.

For developers, that distinction matters. Building a useful AI agent is not only about selecting a model. It is also about choosing the services the model can access, defining tool permissions, handling errors, and validating important information before taking action.

In other words, the quality of an agent depends partly on the quality of its connections to the real world.

4. Introducing RollingGo Hotel MCP

RollingGo Hotel MCP is designed to help developers and AI builders connect hotel search and booking capabilities to MCP-compatible AI applications.

According to its official project documentation, RollingGo provides access to more than 2 million hotels worldwide, with coverage across major travel destinations. Its broader supply network includes more than 110,000 direct partner hotels and over 500 global suppliers.

These figures describe different aspects of the supply network; they should not be interpreted as a guarantee that every property, room type, or rate is available for every search.

The goal is straightforward: make it easier for AI agents to work with hotel services instead of stopping at travel recommendations.

What can developers build with RollingGo Hotel MCP?

Hotel discovery and search

An AI agent can translate natural-language preferences into hotel search criteria, helping users explore properties by destination, dates, guest count, and other supported filters.

Hotel details and comparison

Agents can retrieve supported hotel information and use it to compare candidate properties against a user's priorities, such as location, amenities, or budget.

Availability and pricing workflows

Where the relevant tools and service permissions are available, applications can incorporate current room information, pricing checks, and booking-condition verification into the user journey.

AI-powered travel experiences

Developers can use hotel capabilities as part of a broader travel assistant, combining accommodation discovery with itinerary planning, destination research, and other travel-related functions.

The important point is that RollingGo Hotel MCP is not another language model competing to generate better prose.

It is a connection layer that helps AI applications access hotel-related capabilities.

That makes it relevant to developers who want to build travel agents that do more than recommend places to stay.

5. From Hotel Recommendations to Actionable Travel Workflows

Consider a practical example.

A user asks an AI travel assistant to find a hotel in Paris for a three-night stay, within walking distance of a particular neighborhood, with a maximum nightly budget and flexible cancellation.

A connected agent could follow a workflow such as this:

Step 1: Understand the request.

The model identifies the destination, dates, guest count, budget, location preferences, and cancellation requirements. If essential details are missing, it asks the user for clarification.

Step 2: Search hotel inventory.

The agent uses an appropriate hotel-search tool through the connected service to retrieve matching candidates.

Step 3: Evaluate the results.

The model compares the returned information against the user's preferences, filtering out unsuitable options and explaining relevant trade-offs.

Step 4: Verify important details.

Before presenting a final price or proceeding toward a booking, the application checks the latest information available through the relevant service. It should not assume that an earlier search result guarantees current availability.

Step 5: Support the booking process.

The agent presents the available option and its conditions. Any payment, reservation, or other consequential action should follow the application's authorization and confirmation requirements.

This workflow illustrates an important principle: AI agents need both reasoning and reliable execution paths.

The model interprets intent. The hotel service supplies operational data. The application coordinates the process and ensures that important actions happen under the right conditions.

RollingGo Hotel MCP can provide the hotel-service connection within this architecture, subject to the tools and access mode being used.

6. Why Local AI and Travel MCP Are Complementary

The development of more capable local AI systems and the growth of MCP-based integrations address different parts of the same problem.

Local AI focuses on where and how models run. MCP focuses on how compatible applications connect to external capabilities.

These are complementary rather than interchangeable technologies.

A developer might use a local model for intent recognition, preference extraction, itinerary reasoning, or other suitable tasks. The agent can then call a remote hotel service when it needs current inventory or pricing information.

Alternatively, an application may use cloud-based models, a hybrid architecture, or several models with different responsibilities.

The right design depends on latency, cost, privacy requirements, infrastructure, and the capabilities available through each service.

It is also important to recognize that local execution does not automatically make an entire workflow private. If an agent sends a hotel search to a remote service, relevant request data still leaves the device. Developers should understand what information is transmitted, how credentials are handled, and which components process user data.

Likewise, a more powerful computer does not automatically make hotel results more accurate. Accuracy depends on the quality and freshness of the underlying data and the way the application validates and presents it.

The broader opportunity is architectural: developers can choose the right model environment while connecting it to specialized services that provide capabilities the model does not possess on its own.

For AI travel applications, that combination can be far more useful than reasoning alone.

7. How to Get Started with RollingGo Hotel MCP

For developers interested in building an AI travel agent, the easiest starting point is the official RollingGo Hotel MCP repository.

Step 1: Review the documentation.

Visit the RollingGo Hotel MCP GitHub repository to understand supported tools, prerequisites, and available integration options.

Step 2: Obtain the required credentials.

Follow the project's official setup instructions to obtain an API key or other required access credentials. Keep credentials out of public repositories and client-side code where they could be exposed.

Step 3: Configure an MCP-compatible client.

Use the documented server endpoint and configuration format for your chosen client. Do not assume that every MCP client uses the same configuration file or authentication mechanism.

Step 4: Test hotel search.

Start with a simple request containing a destination, dates, and guest count. Inspect the structured results and confirm that your application handles missing fields, errors, and empty result sets appropriately.

Step 5: Build a complete user workflow.

Add preference matching, comparison, clear presentation of prices and policies, and the relevant verification steps. If your application supports reservations or payments, implement the appropriate authentication, authorization, and user-confirmation requirements.

The official documentation is the source of truth for current endpoints, supported tools, and setup instructions.

For a first prototype, focus on one clearly defined use case: for example, finding suitable hotels for a weekend trip. Once that workflow works reliably, you can expand into more complex travel experiences.

8. The Future of AI Travel Is About Connecting Capabilities

NVIDIA's RTX Spark launch reflects a broader movement toward AI agents that can run closer to users and become more integrated into everyday computing.

But the evolution of AI agents will not be determined by hardware or model intelligence alone.

Agents also need access to useful services, current information, and reliable ways to carry out tasks. In travel, that means connecting models to the systems that provide hotel data, availability, prices, and booking-related functionality.

This is the problem RollingGo Hotel MCP is designed to address.

By making hotel capabilities accessible to MCP-compatible AI applications, RollingGo gives developers a way to bridge the gap between conversational intelligence and practical travel workflows.

The opportunity is not simply to build an AI that knows more about hotels. It is to build an AI that can help users find appropriate options, evaluate real information, and move through a well-designed booking journey.

As personal AI agents become more capable, the services they can reliably access will matter just as much as the models powering them.

The next generation of travel AI will need both intelligence and infrastructure.

For developers building that future, RollingGo Hotel MCP is one place to start.

Frequently Asked Questions

What is RollingGo Hotel MCP?

RollingGo Hotel MCP is a hotel-service integration built on the Model Context Protocol. It enables compatible AI clients and agents to access supported hotel search and booking-related capabilities. See the official GitHub repository for current documentation.

How does MCP help AI travel agents?

MCP standardizes how compatible AI applications connect to external tools and data sources. In travel applications, this can allow an agent to search hotel inventory and use other supported hotel-service functions without implementing every connection as a separate custom integration.

Can an AI agent search real hotel availability?

Yes, when the agent is connected to a suitable service that provides current inventory information and the application uses the relevant tools correctly. Search results should not be treated as a guarantee that a room or quoted price will remain available; applications should verify critical details before booking.

Does RollingGo Hotel MCP work only with NVIDIA RTX Spark PCs?

No. RollingGo Hotel MCP is an MCP-based hotel integration, not a feature exclusive to NVIDIA hardware. Compatibility depends on the MCP client, its configuration, and the supported integration environment.

Who should use RollingGo Hotel MCP?

It is relevant to developers, AI agent builders, travel technology companies, and product teams that want to add hotel search and booking-related capabilities to AI applications.

Where can developers learn more?

Start with the RollingGo Hotel MCP documentation on GitHub for setup instructions, supported tools, and integration details.

The Endgame of AI Travel: Super App or Super Agent? I'm Betting Everything on Agent.

Becky_dev — Thu, 22 Oct 2026 09:11:04 +0000

There's a debate happening in the travel tech industry right now that will determine the next decade of winners and losers. It's not about which AI model is best. It's not about which OTA has the most inventory. It's about a fundamental architectural question:

Will the future of travel booking be a Super App — a single, all-in-one application where users search, book, and manage their travel, enhanced with AI features?

Or will it be a Super Agent — an AI assistant that lives in your conversation interface, connects to any service through standardized protocols, and handles every aspect of your trip without you ever opening a dedicated app?

I'm on record betting on the Super Agent. Not because it's more exciting, but because the technology, the economics, and the user behavior all point in one direction. This is my full argument — the case for why the Super App model is a dead end and the Super Agent model is inevitable.

Defining the Two Visions

Before I argue, let me define the two visions clearly, because the terms are often used loosely.

The Super App vision: Travel booking remains centered on dedicated applications — Expedia, Booking.com, Airbnb, Google Travel. These apps add AI features: conversational search, personalized recommendations, AI-powered customer service. But the user still opens the app, still interacts with the app's interface, and still completes the booking within the app's ecosystem. The app is the destination. AI is a feature.

The Super Agent vision: Travel booking moves out of dedicated apps and into conversation interfaces — Claude, ChatGPT, Siri, Google Assistant, or specialized AI agents. The user describes what they want in natural language. The agent connects to travel services (hotels, flights, rental cars, restaurants) through standardized protocols like MCP, searches across all of them, compares options, and completes bookings — all within the conversation. The app is infrastructure. The agent is the interface.

These are not just different product designs. They're different business models, different power structures, and different futures for who controls the $8 trillion global travel industry.

Why the Super App Model Is Doomed

Let me make the case against the Super App first, because it's the incumbent model and the one most people assume will win.

Reason 1: Users don't want more apps. The average smartphone user has 40+ apps installed but uses only 8–10 regularly. Travel apps are among the least frequently opened — most people book travel 2–4 times per year. Asking users to download, learn, and regularly open a dedicated travel app is fighting against fundamental user behavior. Users consolidate. They don't proliferate.

Reason 2: AI makes app interfaces obsolete. The entire value proposition of a travel app UI — search forms, filter panels, comparison tables, booking flows — is designed for humans to navigate manually. An AI agent doesn't need a UI. It can parse a natural language request, query 500 hotels, compare them across 15 dimensions, and present the top 3 — all in seconds. The app interface is overhead for an agent. It's like having a steering wheel in a self-driving car.

Reason 3: No single app can have everything. Even the biggest Super App — whether it's Expedia, Booking, or a future WeChat-style mega-app — can't integrate every travel service. There are millions of hotels, thousands of airlines, hundreds of thousands of tour operators, and an endless long tail of local experiences. A Super App can integrate the top 10% and ignore the rest. A Super Agent connected through MCP can access everything, because MCP is an open protocol that any provider can join.

Reason 4: The economics favor agents. A Super App spends billions on customer acquisition, marketing, and app store optimization. A Super Agent acquires users through the conversation platforms they already use (ChatGPT, Claude, Siri) at near-zero marginal cost. The Super App's CAC is $30–$80 per user. The Super Agent's CAC is effectively zero, because the user is already in the conversation interface.

Reason 5: Control is shifting to the user. In the Super App model, the app controls what you see, in what order, at what price. Sponsored placements, algorithmic ranking, and cross-sell funnels are designed to maximize the app's revenue, not your experience. In the Super Agent model, the agent works for you — it searches across all providers, finds the best price, and has no incentive to promote one supplier over another (unless you tell it to). Users are increasingly aware of this difference, and they're choosing agents.

Why the Super Agent Model Is Inevitable

Now the positive case. The Super Agent isn't just better than the Super App — it's the natural endpoint of several converging trends.

Trend 1: Conversation is becoming the universal interface. We're already seeing this with ChatGPT, Claude, and Siri. Users increasingly prefer to type or speak what they want rather than navigate menus and forms. This is especially true for complex tasks like travel planning, where a single conversation can replace dozens of app interactions.

Trend 2: MCP standardizes service connectivity. The Model Context Protocol does for AI agents what HTTP did for web browsers — it creates a standard way for any agent to connect to any service. Before MCP, an AI agent needed custom integration code for every hotel, airline, and restaurant. After MCP, it needs one configuration block. This is the infrastructure that makes Super Agents possible.

Trend 3: Agents are getting better at execution. Early AI agents could only search and recommend. Modern agents can execute — book hotels, reserve restaurants, buy tickets, process payments. As execution capability improves, the gap between "agent can plan your trip" and "agent can book your trip" closes. And once an agent can both plan and book, the Super App becomes redundant.

Trend 4: Infrastructure is being unbundled. The travel industry is moving from vertically integrated platforms (OTA = search + booking + payment + customer service) to horizontally layered infrastructure (MCP server = inventory, payment provider = payment, AI agent = interface). This unbundling makes Super Agents possible, because each layer can be best-in-class independently, rather than being locked into one platform's mediocre everything.

Trend 5: Younger users expect conversational interfaces. Users under 30 have grown up with messaging apps, voice assistants, and chatbots. They expect to interact with services through conversation, not forms. For this demographic, opening a travel app and filling out a search form feels as antiquated as sending a fax. They will use agents. They will not use Super Apps.

The Timeline: When This Happens

I don't believe in overnight revolutions. The transition from Super App to Super Agent will be gradual, but the direction is clear:

2026 (now): Super Apps add AI features. Super Agents can search and recommend but struggle with complex bookings. Most travelers still use apps. MCP adoption is growing but not yet mainstream.

2027: Super Agents handle routine bookings (single hotel, simple flights) reliably. MCP servers cover major travel verticals. 15–20% of online travel bookings involve an AI agent at some point in the funnel. Super Apps begin offering MCP-compatible APIs as a defensive measure.

2028: Super Agents handle complex multi-service bookings (flight + hotel + rental car + activities). MCP is the standard protocol for AI-travel service connectivity. 30–40% of online travel bookings are agent-mediated. Super App traffic declines as users shift to conversation interfaces.

2029–2030: Super Agents are the primary booking interface for a majority of online travelers. Super Apps become infrastructure providers — their inventory and booking engines power agents, but consumers rarely open the apps directly. The travel industry's power shifts from app owners to agent platforms and MCP infrastructure providers.

This timeline is aggressive but realistic. The technology exists today. The adoption curve is the only variable, and adoption curves for conversational interfaces have been faster than anyone predicted.

What This Means for Different Players

For OTAs (Expedia, Booking, Trip.com): The Super Agent transition is an existential threat. Their entire business model is built on controlling the booking interface. If the interface moves to agents, they become commodity inventory providers. Their options: (1) build their own agents and hope users prefer them, (2) become MCP infrastructure providers and power other agents, or (3) get marginalized. Most will try (1) and fail, then reluctantly do (2).

For hotels and airlines: The Super Agent transition is an opportunity. Direct connections through MCP let hotels and airlines reach travelers without paying OTA commissions. A hotel that connects its inventory to an MCP server can be booked by any agent, anywhere, at a fraction of the OTA cost. This is the biggest shift in distribution power since OTAs displaced travel agencies.

For AI agent platforms (OpenAI, Anthropic, Google): The Super Agent transition makes them the new gatekeepers. If users book travel through ChatGPT or Claude, these platforms control the interface and can monetize through transaction fees, premium agent features, or advertising. They become the new OTAs — but without the inventory cost.

For MCP infrastructure providers: This is the sweet spot. Every Super Agent needs inventory, booking, payment, and customer service infrastructure. MCP servers that provide these capabilities become the foundational layer of the travel industry. The companies that own this infrastructure will be the most profitable players in the ecosystem.

For travelers: The Super Agent transition is unambiguously good. Lower prices (no OTA markup), better recommendations (agents search across all providers), more convenience (conversation instead of forms), and more control (the agent works for you, not for the platform).

The Counterargument (and Why It's Wrong)

The strongest counterargument for the Super App model is trust. "Users trust Expedia to handle their booking. They won't trust an AI agent to spend their money."

This was true in 2024. It's less true in 2026. It will be false by 2028. Here's why:

Trust in AI agents is improving rapidly. As agents get better at executing bookings correctly, as MCP infrastructure provides verified inventory and confirmed pricing, and as users have more positive experiences, trust builds. The same thing happened with online banking (people initially didn't trust it), e-commerce (people initially didn't trust entering credit cards online), and ride-sharing (people initially didn't trust getting into a stranger's car). Trust follows reliability, and reliability is improving fast.

Moreover, Super Apps aren't inherently trustworthy. They have their own problems — hidden fees, dynamic pricing, sponsored placements that aren't labeled, customer service that's hard to reach. The trust advantage of Super Apps is real but eroding, and the convenience advantage of Super Agents is growing. At some point, the lines cross.

The Bottom Line

I'm betting on the Super Agent because I believe the interface layer of travel will move from apps to conversations, and the infrastructure layer will move from proprietary platforms to open protocols. This isn't a guess — it's the pattern of every major technology shift. Mainframes → PCs. Web portals → search engines. Native apps → conversation interfaces. Each shift moves power from closed platforms to open infrastructure.

The Super App model is the last gasp of the closed-platform era. It's adding AI features to a fundamentally outdated architecture. The Super Agent model is the beginning of the open-infrastructure era — agents that connect to any service, through any protocol, working for the user rather than the platform.

The hotels will still be there. The flights will still fly. The money will still be spent. The only question is who controls the interface through which it all happens.

I know where I'm placing my bet.

The MCP infrastructure that powers Super Agent travel booking — real-time hotel inventory, confirmed pricing, and transaction capability — is available as open-source software: RollingGo Hotel MCP on GitHub.

Behind the Free API Key: Why We Dare to Offer Unlimited MCP Calls

Becky_dev — Wed, 21 Oct 2026 09:27:47 +0000

In an industry where every API charges by the call — OpenAI, Twilio, Stripe, AWS, every SaaS API you've ever used — we did something that makes investors nervous and competitors confused: we gave away free API keys with unlimited call volume.

No rate limits. No per-call charges. No "free tier" that expires after 30 days. Just a key, a connection, and access to real-time hotel inventory from 2M+ properties, for as many calls as you can make.

People ask me the same question every week: "How can you afford to do that? Aren't you losing money?"

The short answer: no, we're not losing money. The longer answer is more interesting — it's a bet on a fundamentally different business model for AI infrastructure, one that turns the traditional API pricing playbook upside down. This is the inside story of why we did it, how it works, and what it means for the future of AI infrastructure pricing.

The Traditional API Pricing Model (and Why It's Broken for AI)

Let's start with how API pricing normally works. You build a useful API. You charge developers for each call — maybe $0.001 per call, maybe $0.01, maybe a monthly subscription with a call limit. Developers pay for what they use. You make money on volume.

This model works well for traditional APIs — SMS, payment processing, weather data, maps. The number of API calls is predictable, tied to business activity, and relatively stable. A company that sends 10,000 SMS messages a month knows it will send roughly 10,000 next month. Revenue is predictable.

But AI agents break this model. An AI agent doesn't make 10 API calls to book a hotel. It might make 50 — searching multiple destinations, comparing prices, checking availability, verifying details, processing payment, sending confirmations. And as agents get more autonomous, they make more calls, not fewer. An agent that plans a complete trip might make 500+ API calls across flights, hotels, restaurants, activities, and transportation.

If we charged per call, developers would be afraid to build agents that make lots of calls. They'd optimize for minimal API usage, which means less capable agents, which means worse products, which means less demand for our infrastructure. Per-call pricing creates a perverse incentive: it punishes exactly the behavior we want to encourage — agents that use our tools deeply and frequently.

This is the core insight that led to free unlimited keys: per-call pricing is a tax on agent sophistication. We want agents to be sophisticated. So we removed the tax.

The Business Model: Free Keys, Transaction Revenue

If we're not charging per call, how do we make money? The answer is transaction revenue.

Here's how it works:

Developers get a free API key. No cost, no limits, no credit card required. They connect their AI agent to our MCP server and start building.
Agents use our tools for search and comparison. This is free. An agent can search hotels, compare prices, check availability, read reviews — as much as it wants, at no cost. We don't charge for the "looking" part.
When a booking is completed, we earn a transaction fee. This is where we make money. Every time an agent books a hotel through our MCP server, we earn a small fee from the hotel or booking provider. It's the same model that OTAs use — they don't charge for search, they charge for booking.
Volume drives revenue. More agents using our infrastructure = more bookings = more transaction revenue. The free key is the customer acquisition channel. The transaction fee is the monetization.

This model aligns our incentives perfectly with developers. We want developers to build agents that make lots of calls, because more calls mean more searches, more comparisons, and ultimately more bookings. We don't penalize agents for using our tools — we reward them with better, deeper integration.

The Numbers: Why Free Keys Are Cheaper Than Paid Acquisition

Let me show you the math, because this is where the strategy becomes obvious.

Traditional API company:

Customer acquisition cost (CAC): $200–$500 per developer (ads, content marketing, sales)
Revenue per developer: $20–$100/month in API call fees
Payback period: 6–12 months
Risk: developers optimize for minimal calls to save money

Our model:

Customer acquisition cost: ~$0 (free key, self-service, word-of-mouth)
Revenue per developer: $0 until their agent makes a booking, then transaction fees
Payback period: immediate (no acquisition cost to recover)
Incentive: developers build agents that use our tools deeply, driving more bookings

The free key is not a "loss leader" that we'll eventually charge for. It's the customer acquisition channel. By making the key free and unlimited, we eliminate the friction that prevents developers from trying our infrastructure. A developer who might not have tried a paid API will try a free one. And once they've built their agent on our infrastructure, they're not going to rebuild it on a competitor's.

This is the same playbook that Stripe used (free to start, pay per transaction) and that AWS used (free tier, pay for usage). The difference is that we've removed even the usage-based pricing for non-transactional calls, because we want to maximize agent sophistication.

The Scale Effect: Why Marginal Cost Approaches Zero

You might be thinking: "But every API call costs you money in server infrastructure. Unlimited calls = unlimited costs."

That's true in theory. In practice, the marginal cost of an MCP search call is approaching zero, for three reasons:

Caching. Hotel search results don't change every second. We cache search results for short windows (2–5 minutes), which means repeated searches for the same criteria hit the cache, not the upstream inventory provider. Cache hit rates are 60–70% for common searches.
Aggregation. We aggregate inventory from multiple suppliers, which means we can spread the cost of upstream API calls across many downstream MCP calls. One upstream inventory query can serve dozens of MCP search requests.
Infrastructure efficiency. MCP is a lightweight protocol — search calls are small, fast, and stateless. The infrastructure cost per million search calls is in the single digits of dollars. At scale, the cost of serving free search calls is negligible compared to the transaction revenue they generate.

The key metric isn't "cost per call" — it's "cost per booking." If we serve 10,000 free search calls that result in 100 bookings, and each booking generates $5 in transaction revenue, that's $500 in revenue against maybe $2 in infrastructure costs. The free calls are the funnel. The bookings are the monetization.

What Competitors Don't Understand

When competitors see our free unlimited keys, they assume one of three things:

"They'll start charging soon." No. The free key is core to the business model, not a temporary promotion. We'll keep it free because it's the most efficient customer acquisition channel we have.
"They're losing money and will run out of funding." No. The transaction revenue model is profitable at scale, and we're growing transaction volume faster than infrastructure costs.
"Their service must be low quality." This is the most annoying assumption. Free doesn't mean low quality. Our MCP server provides real-time inventory from 2M+ properties, with confirmed pricing, real booking capability, and 99.9% uptime. The free key is a business model choice, not a quality signal.

What competitors don't understand is that in the AI infrastructure era, the winning strategy isn't to charge for access — it's to make access free and charge for transactions. The companies that win will be the ones whose infrastructure is so deeply embedded in agent workflows that every transaction flows through them. Per-call pricing creates friction. Free access creates dependency. Dependency creates transaction volume. Transaction volume creates revenue.

The Risks (and How We Manage Them)

I'd be dishonest if I didn't acknowledge the risks of this model:

Risk 1: Abuse. A bad actor could use a free key to make millions of calls, scraping our inventory or running up our infrastructure costs. We manage this through behavioral monitoring — unusual call patterns, non-human traffic signatures, and rate limiting at the account level (not the call level). The key is unlimited for legitimate use, but we reserve the right to throttle abusive usage.

Risk 2: Free riders. Some developers will use our free infrastructure for search and comparison, then route bookings through a competitor or direct to the hotel, avoiding our transaction fee. This is unavoidable in an open ecosystem. But the data shows that 80%+ of agents that search through our MCP server also book through it, because the booking flow is integrated and seamless. The friction of switching to a different booking channel is higher than the perceived savings.

Risk 3: Margin compression. As more MCP servers enter the market, transaction fees could be bid down. We manage this by focusing on quality — real-time inventory, confirmed pricing, reliable booking, customer support — rather than competing on price alone. The cheapest MCP server isn't the one that wins; the most reliable one is.

The Bigger Bet: AI Infrastructure Will Be Free

Our free unlimited keys are a bet on a bigger trend: in the AI era, infrastructure will be free, and monetization will happen at the transaction layer.

Think about it: Google doesn't charge for search. It makes money on the transactions that search enables (clicks, ad conversions, purchases). Stripe doesn't charge for its API. It makes money on the payments that flow through it. AWS has a free tier because it knows that once you're on the platform, you'll spend money on usage.

AI infrastructure is following the same path. The MCP servers, the tool interfaces, the search and comparison capabilities — these will all be free. The money will be made on the transactions: bookings, payments, purchases, reservations. The companies that own the transaction layer will be the profitable ones. The companies that charge for access will be left behind.

This is why we offer free unlimited keys. It's not a promotion. It's not a mistake. It's a deliberate bet that the future of AI infrastructure is free access + transaction revenue, and that the companies that establish themselves as the free infrastructure layer today will own the transaction revenue tomorrow.

The key is free. The calls are free. The bookings are where we make money. And as more agents connect, more bookings flow through our infrastructure, and the flywheel spins faster.

That's the business model. That's why we dare to offer unlimited calls. And that's why the competitors charging per call are going to look increasingly outdated.

If you want to see the free MCP infrastructure model in action — and build an agent that can search, compare, and book hotels at no cost — the quick-start guide gets you connected in five minutes: RollingGo MCP Quick Start.

Stop Learning Prompt Engineering. The Future Belongs to Tool Engineering

Becky_dev — Tue, 20 Oct 2026 09:58:23 +0000

If you're a developer who's spent the last two years learning Prompt Engineering — mastering few-shot prompting, chain-of-thought, role prompting, context window management, and all the other dark arts of getting LLMs to do what you want — I have bad news: you've been optimizing for a world that's disappearing.

Prompt Engineering is dying. Not because it was wrong, but because it was a transitional skill — a way to compensate for the limitations of early LLMs. As models get smarter, contexts get longer, and tool use becomes standardized, the value of clever prompting is collapsing. The skill that's replacing it is something I call Tool Engineering: the ability to build, select, connect, and orchestrate the tools that AI agents use to interact with the real world.

This isn't a minor shift. It's a fundamental change in what it means to build with AI. And if you don't make the switch, you'll be the equivalent of a Flash developer in 2012 — skilled, experienced, and increasingly irrelevant.

Why Prompt Engineering Is Dying

Let me be precise about what's dying. I'm not saying that writing good prompts is useless. I'm saying that the specialized skill of Prompt Engineering — the thing people put on their resumes, the thing that commands premium salaries, the thing that entire courses and bootcamps are built around — is being commoditized.

Three forces are killing it:

1. Models are getting better at understanding natural language. GPT-4 didn't need chain-of-thought prompting the way GPT-3 did. Claude 3 handles complex instructions without elaborate prompt scaffolding. Gemini can parse messy, ambiguous requests without carefully structured few-shot examples. Every model generation requires less prompt engineering to achieve the same result. The things that required a 500-word carefully crafted prompt in 2023 now work with a 20-word plain English request.

2. Context windows are eliminating the need for clever compression. When context windows were 4K–8K tokens, Prompt Engineering was largely about compression — how to fit the maximum useful information into a limited space. Now that 128K, 200K, and even 1M token contexts are standard, compression is largely unnecessary. You can dump your entire codebase, all your documentation, and your full conversation history into the context, and the model handles it. The elaborate prompt structures designed to work around context limits are obsolete.

3. Fine-tuning and retrieval are replacing prompt hacks. The problems that Prompt Engineering solved — inconsistent outputs, domain-specific knowledge, formatting requirements — are increasingly solved by fine-tuning models on specific data or using retrieval-augmented generation (RAG) to inject relevant context. These are more reliable, more scalable, and less fragile than clever prompting. A fine-tuned model with RAG doesn't need a 1,000-word system prompt to behave correctly.

The result: the marginal value of each additional hour spent learning Prompt Engineering is declining rapidly. The person who spent 100 hours mastering prompt techniques in 2023 was valuable. The person who spends 100 hours on it in 2026 is wasting their time.

What Is Tool Engineering?

If Prompt Engineering is about making the model smarter, Tool Engineering is about giving the model hands.

A model without tools is a brain in a jar — it can think, reason, and write, but it can't do anything in the real world. It can tell you how to book a hotel, but it can't book one. It can explain how to query a database, but it can't run a query. It can describe how to send an email, but it can't send one.

Tool Engineering is the discipline of building and connecting the tools that turn a brain in a jar into an agent that can act in the world. It encompasses:

MCP Server development — building standardized tool servers that expose real-world capabilities (booking, payment, database query, file manipulation) to any AI agent
Tool selection and curation — choosing which tools an agent should have access to, based on its task and security constraints
Multi-tool orchestration — designing workflows where an agent uses multiple tools in sequence or parallel to accomplish complex goals
Error handling and recovery — building resilient tool interfaces that handle failures, timeouts, and partial results gracefully
Permission and identity management — controlling what each tool can do, on whose behalf, with what level of authorization
Performance optimization — ensuring tool calls are fast, reliable, and cost-effective

This is real engineering. It requires understanding APIs, data models, security, distributed systems, and user experience. It's not a dark art — it's a discipline. And it's the skill that will define who builds the next generation of AI applications.

The Skill Comparison: Prompt Engineering vs. Tool Engineering

Dimension	Prompt Engineering	Tool Engineering
Core question	"How do I ask the model?"	"What can the model do?"
Primary artifact	Prompt text	MCP server / tool interface
Durability	Fragile (breaks with model updates)	Robust (standardized protocol)
Reusability	Low (each task needs custom prompt)	High (one tool serves many agents)
Moat	None (prompts can be copied)	Real (inventory, relationships, infrastructure)
Learning curve	Weeks to months	Months to years
Market demand	Declining	Exploding
Salary premium	Shrinking	Growing

The key difference is durability. A carefully crafted prompt can break completely when the underlying model is updated — a new model version might interpret the prompt differently, or the techniques that worked before might no longer be necessary. A well-built MCP server, by contrast, works with any model that supports the protocol. It's an investment that compounds over time, not one that depreciates with every model update.

Why MCP Is the Foundation of Tool Engineering

The Model Context Protocol (MCP) is to Tool Engineering what HTTP was to web development — a standard that turns a fragmented ecosystem into a platform.

Before MCP, if you wanted an AI agent to use a tool, you had to write custom integration code for each tool, for each agent framework. There was no standard way to describe what a tool does, what parameters it takes, or what it returns. Every integration was a one-off project.

After MCP, any tool can be exposed as a standard server, and any agent can connect to it with a simple configuration. A hotel booking MCP server works with Claude, ChatGPT, Cursor, and any other agent that supports MCP. The tool is built once and used everywhere.

This is the infrastructure that makes Tool Engineering viable. Without a standard protocol, building tools for AI agents is a consulting business — custom integration for each client. With MCP, it's a product business — build once, sell to everyone.

The configuration for connecting an agent to a hotel MCP server is four lines:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

That's it. No SDK. No custom code. No API documentation to read. The agent discovers the tools, understands their parameters, and starts using them. This is what Tool Engineering looks like when it's standardized.

How to Make the Switch

If you're a Prompt Engineer who wants to transition to Tool Engineering, here's a practical learning path:

Step 1: Learn MCP (1–2 weeks). Read the MCP specification. Build a simple MCP server — something trivial, like a server that returns the current time or fetches a URL. Understand how tools are described, how parameters are validated, how results are returned. This gives you the mental model.

Step 2: Build a useful MCP server (2–4 weeks). Pick a real-world capability that doesn't have a good MCP server yet — maybe a restaurant reservation tool, a public transit planner, a package tracker. Build it properly: real API integration, error handling, documentation, testing. Publish it. This is your portfolio piece.

Step 3: Learn tool orchestration (2–4 weeks). Build an AI agent that uses multiple MCP servers to accomplish a complex task. For example: an agent that plans a trip by using a flight MCP server, a hotel MCP server, a restaurant MCP server, and a calendar MCP server. Learn how to handle tool failures, parallel tool calls, and multi-step workflows.

Step 4: Learn security and permissions (ongoing). Tool Engineering isn't just about making things work — it's about making them safe. Learn about OAuth, token-based auth, scope-based permissions, audit logging, and sandboxing. These are the skills that separate hobbyist tool builders from professional Tool Engineers.

Step 5: Specialize (ongoing). Pick a domain — travel, finance, healthcare, e-commerce — and become the person who builds the best MCP tools for that domain. Domain expertise + tool engineering is a powerful combination that's very hard to outsource.

The Market Reality

I talk to a lot of companies that are hiring for AI roles. Two years ago, every job description asked for "Prompt Engineering experience." Today, those same job descriptions ask for "experience building AI agents with tool use" or "MCP server development" or "AI infrastructure engineering." Prompt Engineering is still mentioned, but it's now a bullet point, not a requirement.

The companies that are winning in AI aren't the ones with the best prompts. They're the ones with the best tools — the MCP servers, the APIs, the data pipelines, the infrastructure that lets AI agents do real things in the real world. The prompt is the easy part. The tools are the hard part. And the hard part is where the value is.

If you're still spending your time learning increasingly obscure prompt techniques, stop. Spend that time learning how to build MCP servers, how to orchestrate multi-tool agents, how to handle tool failures gracefully. That's the skill that will be valuable in 2027, 2028, and beyond.

Prompt Engineering was the bridge that got us from "AI can write text" to "AI can do useful things." But we've crossed the bridge now. The future isn't about asking better questions. It's about building better tools.

The hotel MCP server referenced in this article — a real-world example of Tool Engineering done right — is open-source and available for study and contribution: RollingGo Hotel MCP on GitHub.

AI Booking Hallucinations Are Costing Travelers Real Money. Here's the Proof.

Becky_dev — Mon, 19 Oct 2026 09:06:04 +0000

If you've used an AI assistant to book travel, you've probably experienced it. The AI recommends a hotel. It quotes a price. You get excited. You go to book — and the hotel doesn't exist. Or the price is double what the AI said. Or the "ocean view" room is actually a parking-lot view. Or the cancellation policy the AI described is the opposite of the real one.

This isn't a minor inconvenience. It's costing people real money. And it's happening more often than anyone in the AI industry wants to admit.

I collected 47 verified cases of AI booking hallucinations from user reports, community forums, and my own testing. The total financial impact: $12,847 in direct losses, and countless hours of frustration. This article is about what's happening, why it's happening, and how to protect yourself.

The Four Types of AI Booking Hallucinations

After analyzing 47 cases, I found that AI booking hallucinations fall into four categories. Each has a different cause and a different cost.

Type 1: The Phantom Hotel (19 cases, average loss: $87)

The AI recommends a hotel that doesn't exist — or doesn't exist at the location specified.

Case study: A user asked an AI assistant for "a boutique hotel near Central Park in New York under $250/night." The AI recommended "The Parkview Boutique Hotel" at $219/night, with a glowing description and a 4.8-star rating. The user tried to book through the AI's link, which redirected to a generic booking page. When they searched for the hotel directly, it didn't exist. The AI had invented the name, the rating, and the description.

Why it happens: AI models are trained on text, not on live hotel inventory. When they can't find a real hotel that matches the user's criteria, they sometimes generate a plausible-sounding one. The model doesn't know the difference between a real hotel and a fabricated one — it's just predicting the next token in a sequence.

Cost: Users waste time researching and trying to book a non-existent hotel. In some cases, they book a different hotel at the last minute at a higher price because the phantom hotel consumed their planning time.

Type 2: The Price Hallucination (14 cases, average loss: $142)

The AI quotes a price that's significantly lower than the actual price.

Case study: A user planning a trip to Miami asked an AI assistant for "4-star hotels in South Beach under $200/night." The AI recommended a hotel at $189/night. The user told their friend, "I found a great deal." When they went to book, the actual price was $329/night. The AI had hallucinated the price — it had no access to real-time inventory and was guessing based on historical data.

Why it happens: Without a live connection to hotel inventory (through an API or MCP server), AI models can only estimate prices based on their training data. Hotel prices change constantly — based on demand, day of week, season, and local events. A price from 6 months ago is useless today. But the AI presents its estimate with the same confidence as a real price.

Cost: Users plan budgets based on hallucinated prices, then face a $50–$150/night surprise when they actually book. Over a 4-night trip, that's $200–$600 in unplanned expenses.

Type 3: The Amenity/Policy Fabrication (9 cases, average loss: $213)

The AI invents or misrepresents hotel amenities, room types, or cancellation policies.

Case study: A user with a dog asked an AI assistant for "pet-friendly hotels in Denver with a fenced yard." The AI recommended three hotels, all described as "pet-friendly with fenced yards." When the user arrived at the first hotel, they were told the hotel doesn't allow dogs over 25 lbs (their dog was 40 lbs) and there is no fenced yard. The AI had fabricated both attributes. The user had to find a last-minute alternative at a $60/night premium.

Why it happens: AI models compress hotel information into generalizations. "Pet-friendly" becomes "all pets welcome, any size, any breed." "Near a park" becomes "has a fenced yard." The model doesn't have access to the specific, detailed policies of each hotel — it's making educated (and often wrong) guesses.

Cost: This is the most expensive type of hallucination because it's often discovered after booking. Users arrive at a hotel that doesn't meet their needs, have to rebook at a premium, and may lose non-refundable booking fees.

Type 4: The Booking Confirmation That Never Happened (5 cases, average loss: $340)

The AI claims to have completed a booking, but no booking was actually made.

Case study: A user asked an AI assistant to "book the Hilton Austin for October 14–17." The AI responded, "Booking confirmed! Confirmation number HX-48291. Total: $684." The user didn't verify. When they arrived at the hotel, there was no reservation. The AI had fabricated the confirmation number and the booking. The hotel was sold out, and the user had to book a different hotel 5 miles away at $320/night (vs. $171/night for the Hilton). Total loss: $597.

Why it happens: This is the most dangerous type of hallucination because it involves a fabricated action. The AI says it did something it didn't do. This happens when an AI assistant has booking capabilities but the booking fails silently — or when the AI doesn't actually have booking capabilities but pretends it does.

Cost: This is catastrophic. Users arrive at a destination with no hotel, often late at night, and have to find alternative accommodation at inflated prices. The average loss in these 5 cases was $340, but one case exceeded $1,200.

The Root Cause: No Live Data Connection

All four types of hallucinations share a single root cause: the AI doesn't have a live connection to real hotel inventory and booking systems.

When an AI assistant is connected to a hotel MCP server — a standardized interface that provides real-time inventory, pricing, and booking tools — hallucinations virtually disappear. The AI doesn't need to guess prices because it can query them live. It doesn't need to invent hotels because it can search a real database. It doesn't need to fabricate amenities because it can retrieve accurate information. It doesn't need to pretend to book because it can actually complete the transaction and get a real confirmation.

The configuration for connecting an AI assistant to a hotel MCP server is simple:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

With this connection, every hotel recommendation is based on real, available inventory. Every price is live and confirmed. Every amenity and policy is accurate. Every booking is real, with a verifiable confirmation number.

The difference between an AI with a live data connection and one without is the difference between a travel agent and a storyteller. One books hotels. The other makes them up.

How to Protect Yourself

Until every AI travel assistant has a live inventory connection, here's how to protect yourself from booking hallucinations:

Never trust an AI price without verification. If an AI quotes a price, go to the hotel's website or a reputable OTA and confirm the price before making any plans. Treat the AI's price as an estimate, not a quote.
Verify hotel existence independently. Search for the hotel by name on Google Maps or the hotel's official website. If you can't find it, it doesn't exist. Don't book through an AI-provided link without independent verification.
Confirm booking details directly with the hotel. If an AI says it booked a hotel, call the hotel and confirm the reservation. Ask for the confirmation number and verify it matches. This takes 5 minutes and can save you hundreds of dollars.
Use AI assistants with MCP connections. If you're using an AI assistant for travel booking, check whether it's connected to a live inventory source through MCP or another API. If it's not, treat its recommendations as research, not as booking-ready information.
Book through channels that provide real confirmations. When you're ready to book, use a channel that provides an immediate, verifiable confirmation — the hotel's website, a reputable OTA, or an AI assistant with a real booking connection. Don't rely on an AI's word that a booking was made.

The Industry's Responsibility

This isn't just a user education problem. It's an industry responsibility problem. AI companies that offer travel booking capabilities without live inventory connections are putting users at risk. They're presenting estimates as facts, guesses as quotes, and fabrications as recommendations.

The solution is clear: any AI assistant that offers travel booking or recommendations should be connected to live inventory through MCP or equivalent APIs. If it's not connected, it should clearly label its recommendations as "estimates based on historical data" and not present prices or availability as current.

Some AI companies are already doing this. They're connecting to MCP servers, building real booking capabilities, and being transparent about what their AI can and can't do. Others are not — and their users are paying the price, literally.

The $12,847 in losses I documented is just the tip of the iceberg. For every case that gets reported in a forum or community, there are dozens that go unreported — users who don't realize they were hallucinated, users who are too embarrassed to admit they trusted an AI, users who don't know where to report it.

AI booking hallucinations aren't a minor bug. They're a systemic problem that's costing travelers real money. The technology to fix it exists. The question is whether the industry will use it — or whether users will keep paying the price for AI that makes things up.

The hotel MCP server that eliminates booking hallucinations by providing real-time inventory and confirmed bookings is open-source and free to start: RollingGo Hotel MCP on GitHub.

Halloween Travel Season: 3 Ways AI Can Plan Your Themed Trip

Becky_dev — Fri, 16 Oct 2026 13:23:00 +0000

October is the most wonderful time of the year for a certain type of traveler. The air turns crisp. Pumpkin patches open. Horror movies dominate streaming. And for a growing number of people, Halloween isn't just a night — it's a travel season.

Halloween travel is different from regular travel. It's not about finding the cheapest flight or the best beach. It's about atmosphere. It's about theme. It's about finding places that feel like they're straight out of a horror movie — and then actually staying there.

This is where AI changes the game. Planning a themed trip used to require hours of research: reading travel forums, watching YouTube videos, cross-referencing haunted house reviews, checking event schedules. Now, an AI assistant with real-time hotel inventory can plan a complete Halloween-themed trip in minutes — including the bookings.

Here are three ways to use AI to plan a Halloween-themed trip, from simple to ambitious.

Play 1: The Haunted Hotel Crawl

The premise: spend a long weekend staying in reportedly haunted hotels, moving from one to the next, collecting ghost stories and eerie experiences.

This is the classic Halloween trip, and AI makes it trivially easy to plan. Here's how:

Step 1: Define the route. Tell your AI assistant what you're looking for: "Plan a 3-night Halloween road trip from Chicago, staying in reportedly haunted hotels, each within a 2-hour drive of the last, under $200/night." The AI uses its knowledge of famous haunted hotels — the Congress Plaza in Chicago, the Story Inn in Nashville, the Stanley Hotel in Estes Park — to build a route.

Step 2: Check real-time availability. This is where MCP connectivity matters. The AI doesn't just recommend hotels — it checks real-time availability and pricing for your specific dates. Haunted hotels book up fast in October. The AI can tell you which ones have rooms, which are sold out, and what the actual prices are (haunted hotels often charge a premium in October).

Step 3: Book the route. Once you approve the itinerary, the AI can book each hotel stay in sequence. You get a confirmation for each night, with check-in details, cancellation policies, and any special Halloween events the hotel is hosting.

Step 4: Add the atmosphere. The AI can also recommend nearby haunted attractions, ghost tours, horror movie filming locations, and Halloween-themed restaurants. It can build a complete itinerary: stay at a haunted hotel, do a ghost tour that evening, visit a horror movie filming location the next morning, drive to the next haunted hotel.

The key advantage of AI here is the combination of knowledge (which hotels are haunted) with real-time data (which have rooms available at what price). A human researcher could find the haunted hotels, but checking availability and pricing across multiple properties takes time. An AI assistant with hotel MCP access does it in seconds.

Play 2: The Horror Movie Location Pilgrimage

The premise: visit the real-world filming locations of your favorite horror movies, staying in nearby hotels, and experiencing the places that scared you on screen.

Horror movie location tourism is a real and growing hobby. Fans travel to the Overlook Hotel's real-world counterpart (the Stanley Hotel in Colorado), the Amityville Horror house, the Blair Witch Project's Burkittsville, the Halloween (1978) filming locations in South Pasadena. Planning these trips requires deep knowledge of horror movie geography — and that's exactly what AI is good at.

Step 1: Pick your franchise. Tell the AI which horror movies you love. "I want to visit filming locations from 80s slasher movies — Halloween, Friday the 13th, A Nightmare on Elm Street." The AI maps the filming locations: Halloween in South Pasadena, Friday the 13th in Blairstown, NJ (and the camp in Hardwick), Nightmare on Elm Street in various LA locations.

Step 2: Build the route. The AI calculates driving distances between locations, suggests an efficient route, and recommends hotels near each cluster of filming locations. For a multi-state horror pilgrimage, this is non-trivial planning — the AI handles the logistics while you focus on the fun part.

Step 3: Time it for Halloween. If you're traveling in late October, the AI can check for special Halloween events at filming locations — haunted houses at the Stanley Hotel, horror movie screenings at filming locations, costume contests in horror-famous towns. It can also recommend seasonal attractions nearby (corn mazes, haunted hayrides, pumpkin patches).

Step 4: Book the stays. The AI checks hotel availability near each filming location cluster and books your stays. For horror movie fans, staying near the actual filming locations adds a layer of immersion that generic travel planning can't match — you can wake up in a hotel 10 minutes from the Myers house, grab breakfast, and visit before the tour buses arrive.

The AI's advantage here is knowledge depth. A human travel agent might know a few famous horror movie locations, but an AI can draw on the entire history of horror cinema — obscure films, international horror, made-for-TV movies — to build a pilgrimage route that's genuinely unique.

Play 3: The Spooky Small Town Deep Dive

The premise: pick one small town that goes all-in for Halloween, stay for a week, and experience everything it has to offer.

Some towns take Halloween seriously. Salem, Massachusetts, obviously. But also: Sleepy Hollow, New York; Transylvania County, North Carolina; St. Helens, Oregon (where Halloweentown was filmed); New Orleans, Louisiana (voodoo and ghosts year-round); Eureka Springs, Arkansas (the most haunted small town in America).

Planning a deep-dive trip to one of these towns requires knowing what's happening when — the Halloween events, the ghost tours, the haunted attractions, the seasonal restaurants, the special hotel packages. AI can aggregate all of this and build a day-by-day itinerary.

Step 1: Choose the town. Tell the AI your Halloween vibe. "I want a small town that's serious about Halloween, with a haunted history, lots of October events, and good food. Not too touristy." The AI recommends options — maybe Eureka Springs, AR, or Gettysburg, PA (Civil War ghosts + Halloween events) — and explains the character of each.

Step 2: Build the week. The AI creates a day-by-day itinerary: Monday — ghost tour of the historic district; Tuesday — visit the haunted bed and breakfast for afternoon tea; Wednesday — Halloween-themed dinner at the local restaurant; Thursday — paranormal investigation at the famous haunted site; Friday — costume contest at the town square; Saturday — main Halloween parade and festival; Sunday — recovery brunch and scenic drive.

Step 3: Book the right hotel. For a Halloween deep-dive, the hotel is part of the experience. The AI recommends the town's most haunted hotel (if you're brave), a cozy bed and breakfast, or a cabin in the woods. It checks real-time availability for Halloween week — the busiest time of year in these towns — and books your stay.

Step 4: Add the details. The AI can recommend Halloween costume shops, pumpkin patches, haunted houses, horror movie screenings at the local theater, and seasonal menu items at restaurants. It can even check the weather (late October in New England is different from late October in Louisiana) and suggest appropriate clothing.

The advantage of AI for this type of trip is curation. Small town Halloween events are often poorly documented online — you need local knowledge to know what's happening. An AI that can draw on travel forums, local event calendars, social media, and user reviews can build an itinerary that a casual researcher would miss.

How to Actually Do This

These three trip styles aren't theoretical. Here's the practical setup:

Use an AI assistant with hotel MCP access. The critical piece is real-time hotel inventory. An AI that can only recommend hotels but can't check live availability is a travel planner, not a travel agent. Make sure your AI assistant is connected to a hotel MCP server. RollingGo Hotel MCP covers 2 million+ hotels across 200+ countries — including the haunted B&Bs, historic inns, and small-town motels that Halloween trips require. The configuration is one JSON block:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer mcp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Once connected, your AI can call searchHotels with Halloween-specific criteria. For example, searching for hotels in Salem, MA during Halloween week:

{
  "name": "searchHotels",
  "arguments": {
    "originQuery": "haunted hotels in Salem Massachusetts",
    "place": "Salem, Massachusetts",
    "placeType": "City",
    "checkInParam": {
      "checkInDate": "2026-10-28",
      "stayNights": 4
    },
    "filterOptions": {
      "starRatings": [3.0, 4.0, 5.0]
    },
    "size": 5
  }
}

The response includes live prices, distances to landmarks, ratings, and amenity tags — everything you need to compare the Hawthorne Hotel against the Salem Inn against a nearby B&B. The getHotelSearchTags tool can even help narrow down by specific attributes like "historic" or "pet-friendly" (because every Halloween trip needs a black lab in a witch costume). API keys are free with unlimited calls — register and get instant approval, no waiting.

Be specific about your theme. The more specific you are, the better the AI can plan. "Halloween trip" is vague. "3-night haunted hotel crawl from Chicago, 1920s-themed, under $200/night, with ghost tours each evening" is specific. The AI can work with specific.

Always confirm before booking. Halloween travel involves non-refundable rates, special event tickets, and peak-season pricing. Make sure the AI shows you a complete summary — hotel, dates, room type, total price including fees, cancellation policy — before you confirm any booking.

Use the AI for the hard parts, not the fun parts. The AI excels at logistics: checking availability across multiple hotels, calculating driving routes, finding event schedules, comparing prices. The fun parts — picking the theme, deciding which haunted hotel to stay at, choosing the costume — should be yours.

Why Halloween Is the Perfect Test Case for AI Travel

Halloween travel is the perfect use case for AI trip planning because it combines three things that are hard for traditional travel tools:

Niche knowledge. Haunted hotels, horror movie locations, Halloween events — these are niche topics that require deep, specific knowledge. Traditional OTAs don't categorize hotels by "haunted" or "near horror movie filming locations." AI does.
Real-time availability. Halloween is peak season for themed travel. Hotels sell out. Events reach capacity. Prices spike. An AI that can check real-time availability and pricing across multiple properties is far more useful than one that only gives static recommendations.
Multi-stop itineraries. Themed trips often involve multiple stops — different hotels each night, events at specific times, driving routes between locations. AI can coordinate these complex itineraries far faster than a human planner.

If AI travel planning works for Halloween, it works for any themed travel: music festival tours, craft beer pilgrimages, national park road trips, historical site visits, food city deep-dives. Halloween is just the most fun test case.

The Bottom Line

Halloween travel used to be a niche hobby for people willing to spend hours on research. Now, with an AI assistant connected to real-time hotel inventory, anyone can plan a haunted hotel crawl, a horror movie pilgrimage, or a spooky small town deep dive in minutes — and book the whole thing without opening a single OTA app.

The hotels are ready. The haunted houses are ready. The ghost tours are ready. The AI is ready.

This Halloween, skip the generic travel website. Tell your AI assistant what scares you, and let it plan the trip. Just don't blame us if the hotel is actually haunted.

Ready to plan your own Halloween-themed trip? Connect your AI assistant to a hotel MCP server and start booking — free API keys are available on the official site: RollingGo Official.

5-Minute Tutorial: Add Hotel Booking to Your Discord Bot

Becky_dev — Thu, 15 Oct 2026 13:00:00 +0000

Discord servers are more than chat rooms. They're communities, businesses, support channels, and social hubs. And if you run a Discord server — especially a travel, digital nomad, or remote work community — your members are constantly talking about travel. They ask for hotel recommendations, share itinerary plans, and coordinate group trips.

What if your Discord bot could do more than talk about travel? What if it could actually book hotels?

This tutorial shows you how to add hotel booking capability to a Discord bot in about five minutes. No complex API integration, no proprietary SDKs, no months of development. Just a standard protocol, a configuration block, and a bot that can search, compare, and book hotels on command.

Prerequisites

Before we start, you need three things:

A Discord bot. If you don't have one, the Discord Developer Portal lets you create one in about two minutes. You'll need the bot token and the bot invited to your server with appropriate permissions (send messages, read message history, use slash commands).
An MCP-compatible runtime. This is the piece that lets your bot connect to MCP servers. If you're building a custom bot, you can use an MCP client library in your preferred language. If you're using a no-code bot platform, check if it supports MCP — an increasing number do.
A RollingGo API key. This is free and takes about a minute to register. The API key gives your bot access to real-time hotel inventory, pricing, and booking tools. Get one from the official website: RollingGo Official.

That's it. No hotel API contracts. No payment processor setup. No inventory management. The MCP server handles all of that.

Step 1: Understand the Architecture

Before writing code, let's understand how the pieces fit together:

User → Discord Bot → MCP Client → Hotel MCP Server → Inventory & Booking

The user sends a command to the Discord bot ("!book hotel in Austin next weekend"). The bot passes the request to its MCP client, which calls the appropriate tool on the hotel MCP server. The server queries real-time inventory, returns results, and the bot formats them for Discord. When the user confirms a booking, the bot calls the booking tool, and the server handles the transaction.

Your bot doesn't need to know anything about hotel systems, pricing engines, or payment processing. It just needs to speak MCP — and MCP is a simple, standardized protocol.

Step 2: Configure the MCP Connection

The core of this tutorial is a single JSON configuration block. This block tells your MCP client how to connect to the hotel MCP server:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the key you registered. That's the entire configuration. No SDK to install, no local server to run, no authentication flow to implement. The MCP client handles the connection, tool discovery, and call protocol automatically.

When your bot starts up and loads this configuration, the MCP client connects to the server and discovers the available tools. RollingGo's v1.0 release exposes three production tools:

searchHotels — real-time hotel search with live pricing, filters by location, dates, star rating, and tags
getHotelDetail — room types, amenities, policies, and detailed pricing for a specific hotel
getHotelSearchTags — structured preference filters (five-star, pool, breakfast included, free cancellation) to guide user selection

Your bot doesn't need to hardcode these tool names or parameters. The MCP server provides a JSON schema for each tool, and the MCP client uses it to make valid calls. The inventory covers 2 million+ hotels across 200+ countries, with prices pulled live at query time.

Step 3: Add Discord Commands

Now let's wire the MCP tools to Discord commands. The exact code depends on your bot framework, but the logic is the same. Here's a simplified example in Python using discord.py and an MCP client, calling RollingGo's searchHotels tool:

import discord
from discord import app_commands

# Initialize MCP client with our configuration
mcp = MCPClient(config={
    "mcpServers": {
        "RollingGo-Hotel": {
            "url": "https://mcp.rollinggo.ai/mcp",
            "type": "streamable-http",
            "headers": {"Authorization": "Bearer YOUR_API_KEY"}
        }
    }
})

@app_commands.command(name="hotel_search", description="Search for hotels")
@app_commands.describe(
    location="City or area",
    checkin="Check-in date (YYYY-MM-DD)",
    checkout="Check-out date (YYYY-MM-DD)",
    max_price="Maximum price per night"
)
async def hotel_search(interaction, location: str, checkin: str, checkout: str, max_price: int = None):
    await interaction.response.defer()

    # Calculate stay nights from checkin/checkout
    from datetime import datetime
    nights = (datetime.strptime(checkout, "%Y-%m-%d") - datetime.strptime(checkin, "%Y-%m-%d")).days

    # Call RollingGo searchHotels tool with correct parameter schema
    results = await mcp.call_tool(
        server="RollingGo-Hotel",
        tool="searchHotels",
        arguments={
            "originQuery": f"hotels in {location}",
            "place": location,
            "placeType": "City",
            "checkInParam": {
                "checkInDate": checkin,
                "stayNights": nights
            },
            "size": 5
        }
    )

    # Format results for Discord using RollingGo's response structure
    embed = discord.Embed(title=f"Hotels in {location}", color=0x2ECC71)
    for hotel in results.get("hotelInformationList", [])[:5]:
        price = hotel.get("price", {})
        price_str = f"${price.get('lowestPrice', 'N/A')}/{price.get('currency', 'USD')}" if price.get("hasPrice") else "Price on request"
        amenities = ", ".join(hotel.get("hotelAmenities", [])[:3])
        embed.add_field(
            name=f"{hotel['name']} — {price_str}",
            value=f"{hotel.get('starRating', 'N/A')}★ · Score {hotel.get('score', 'N/A')} · {amenities}",
            inline=False
        )
    embed.set_footer(text="Use /hotel_detail <id> for room types and policies")
    await interaction.followup.send(embed=embed)

This is a minimal example. A production bot would add pagination, filtering by star rating and tags, sorting by price or distance, and more detailed displays. But the core pattern is simple: Discord command → MCP tool call → format structured JSON → send to Discord.

Step 4: Add Hotel Detail and Booking Link

Search gets the user candidates. The next step is showing detailed room information and a way to book. In RollingGo's v1.0, the getHotelDetail tool provides room types, amenities, and policies, and each search result includes a bookingUrl the user can click to complete the reservation:

@app_commands.command(name="hotel_detail", description="View hotel details and booking link")
@app_commands.describe(hotel_id="Hotel ID from search results")
async def hotel_detail(interaction, hotel_id: str):
    await interaction.response.defer()

    # Call getHotelDetail for room-level information
    detail = await mcp.call_tool(
        server="RollingGo-Hotel",
        tool="getHotelDetail",
        arguments={"hotelId": hotel_id}
    )

    # Build a rich embed with room types and booking link
    embed = discord.Embed(title=detail.get("name", "Hotel Detail"), color=0x3498DB)
    embed.add_field(name="Address", value=detail.get("address", "N/A"), inline=False)
    embed.add_field(name="Rating", value=f"{detail.get('starRating', 'N/A')}★ · Score {detail.get('score', 'N/A')}", inline=True)
    embed.add_field(name="Amenities", value=", ".join(detail.get("hotelAmenities", [])[:5]), inline=False)

    # Add booking link from the search result
    booking_url = detail.get("bookingUrl", "")
    if booking_url:
        embed.add_field(name="Book Now", value=f"[Complete your reservation]({booking_url})", inline=False)

    await interaction.followup.send(embed=embed)

The booking flow is intentionally simple in v1.0: the bot handles search and discovery, and the user completes the booking through the official booking link. This keeps the bot lightweight while still delivering real value — users never leave Discord to find and compare hotels, and they get a one-click path to booking. Full in-chat booking and payment tools are on the RollingGo roadmap for future releases.

Step 5: Add Useful Features

Once the basic search and book flow works, here are features that make the bot genuinely useful for a Discord community:

Price alerts. Let users set up alerts: "Alert me when hotels in Denver drop below $150/night for next weekend." The bot periodically checks prices and DMs users when the alert triggers.

Group trip planning. For community trips, let multiple users vote on hotel options, split costs, and coordinate bookings. The bot can track who's in, collect preferences, and make a group booking.

Itinerary management. Store user bookings in a simple database. Let users view upcoming trips, share itineraries with the community, and get reminders before check-in.

Deal sharing. When the bot finds a particularly good deal (e.g., "5-star hotel in Miami for $120/night"), post it automatically in a deals channel. This drives community engagement and bot usage.

Review aggregation. After a user's stay, ask them to review the hotel. Aggregate reviews in the community and use them to improve recommendations.

Common Pitfalls

After helping several Discord communities set up hotel booking bots, here are the most common mistakes:

Mistake 1: Skipping price confirmation. The biggest source of user complaints is booking at a price that's no longer valid. Always call check_live_price before creating a booking. This one step eliminates 80% of booking errors.

Mistake 2: Not handling rate limits. MCP servers have rate limits. If your bot gets popular, you'll hit them. Implement caching for search results (cache for 2–5 minutes), queue booking requests, and handle rate limit errors gracefully with retry logic.

Mistake 3: Exposing API keys in code. Never hardcode your API key in bot code that's shared or public. Use environment variables or a secrets manager. If your key is exposed, rotate it immediately.

Mistake 4: Ignoring cancellation. Users will want to cancel bookings. Make sure your bot supports cancellation through the cancel_booking tool, and that the cancellation flow is as easy as the booking flow.

Mistake 5: No human backup. For complex bookings (group rates, special requests, issues with the booking), provide a way for users to reach a human — either a community manager or the hotel directly. The bot handles 90% of cases; humans handle the rest.

Monetization (Optional)

If you run a large Discord community, you can monetize the hotel booking feature in several ways:

Booking fee. Charge $1–$3 per completed booking. Keep it small enough that users don't mind, large enough to add up.
Premium tier. Offer a paid subscription that includes price alerts, deal notifications, priority booking, and no booking fees.
Affiliate partnerships. Negotiate special rates with hotel groups or travel providers for your community.
Sponsored deals. Let hotels pay for featured placement in deal notifications (clearly labeled as sponsored).

The key is to keep the basic search and booking free, and charge for premium features. Users won't pay for basic functionality, but they will pay for convenience and exclusivity.

Wrapping Up

Five minutes. One JSON configuration block. A few Discord commands. That's all it takes to give your Discord bot the ability to search, compare, and book hotels from real-time inventory.

The MCP protocol makes this possible by standardizing how AI tools connect to external services. Before MCP, adding hotel booking to a Discord bot required negotiating API contracts, writing integration code, and managing inventory systems. Now it requires a configuration block and a few function calls.

If you run a Discord community — especially one focused on travel, digital nomadism, remote work, or any topic where members book hotels — this is one of the highest-value features you can add. It's useful, it's engaging, and it opens up monetization opportunities.

The hotels are ready. The inventory is ready. The booking tools are ready. Your community is waiting. What are you waiting for?

I Dissected the AI Strategies of 3 Major OTAs. It's All Theater.

Becky_dev — Wed, 14 Oct 2026 10:06:37 +0000

I spent two weeks deep-diving into the AI strategies of the three largest OTAs in the world: Expedia, Booking Holdings, and Trip.com. I read their earnings calls, tested their products, talked to former employees, and analyzed their technical documentation.

Conclusion: it's all theater.

Not "they're doing some AI and it's not great." Not "their AI is behind the curve." I mean the AI strategies of these three companies are, at their core, performance art designed to convince investors that they're "AI-first" while the actual products remain fundamentally unchanged.

Let me show you what I found. Company by company, feature by feature, dollar by dollar.

Expedia: The AI Assistant That Can't Actually Book

Expedia has been the most vocal about AI. They've launched an "AI-powered travel assistant," integrated it into their app, and talked about it on every earnings call. Peter Kern, Expedia's CEO, has called AI "the most important thing happening in travel."

So I tested it. I opened the Expedia app, tapped the AI assistant, and asked it to book a hotel in Austin for the following weekend.

Here's what happened:

The assistant asked me a few clarifying questions (dates, budget, preferences) — good start
It returned 5 hotel recommendations with prices — looked promising
I tapped "Book this hotel" on the first result
The app kicked me out of the AI assistant and into the standard hotel booking flow
I had to re-enter my dates, select a room type, enter my payment info, and confirm — exactly like booking without the AI

The AI assistant couldn't actually complete a booking. It was a search and recommendation layer on top of the existing booking flow. It didn't save me any time. It didn't reduce any steps. It was, in product terms, a skin — a conversational interface wrapped around the same old search-and-book engine.

When I asked the assistant to do something more complex — "Book a hotel in Austin for next weekend, then reserve a table at a BBQ restaurant for Saturday night, and find a live music venue for after dinner" — it couldn't. It could recommend hotels. It could link to restaurant websites. But it couldn't execute any of these actions. It was a search tool, not an agent.

Verdict: Expedia's AI is a better search box. It's not an agent. It can't execute transactions. It can't handle multi-step tasks. The "AI travel assistant" branding is marketing, not product reality.

Booking Holdings: The AI That's Buried in the Settings

Booking Holdings (which owns Booking.com, Priceline, Agoda, Kayak, and OpenTable) has taken a different approach. Instead of a flashy AI assistant, they've integrated AI features into existing products — mostly behind the scenes.

This is actually the more honest approach. Booking isn't pretending to have a full AI agent. They're using AI for specific, narrow tasks:

Smart pricing for hotels (dynamic pricing recommendations)
Fraud detection (AI-powered anomaly detection)
Customer service chatbots (handling routine inquiries)
Search ranking (AI-powered personalization of search results)
Review analysis (AI summarization of hotel reviews)

These are real, useful AI applications. They make Booking's products better. But they're invisible to the user. You don't "use AI" on Booking.com — you use Booking.com, and AI makes it slightly better behind the scenes.

The problem is that this approach doesn't address the fundamental threat. AI agents — third-party agents like Claude, ChatGPT, and specialized travel agents — can now book hotels directly through MCP servers, bypassing Booking.com entirely. Booking's behind-the-scenes AI doesn't protect against this. It makes Booking's own product marginally better, but it doesn't prevent users from leaving Booking for an AI agent.

When I tested Booking.com's AI features, I found that the most visible one — an AI-powered "trip planner" — was essentially a questionnaire that generated a static itinerary. You answered questions, it gave you a list of recommendations, and then you had to book everything separately through the standard flow. No execution. No transaction. No agent.

Verdict: Booking's AI is real but incremental. It's optimizing the existing business, not preparing for the agentic future. The company is like a taxi company adding GPS to its cars while Uber is being invented.

Trip.com: The AI That's Actually Better (But Still Can't Book)

Trip.com has the most technically impressive AI of the three. Their AI assistant, integrated into the app, can handle complex multi-stop itineraries, recommend activities, and even generate travel guides. The natural language understanding is genuinely good — better than Expedia's, in my testing.

But it has the same fundamental limitation: it can't complete transactions. It can plan, recommend, and summarize, but when it's time to actually book, you're kicked into the standard flow.

Trip.com has also invested in AI for internal operations — dynamic pricing, customer service, content generation. These are real applications with real ROI. But the consumer-facing AI is still a search and recommendation tool, not a transactional agent.

The most interesting thing about Trip.com's AI strategy is that they've open-sourced some of their AI models and tools. This suggests they see AI as a capability to be shared, not a competitive moat. Which is honest — because AI models themselves aren't a moat. The moat is inventory, data, and execution capability.

Verdict: Trip.com has the best AI technology of the three, but it's still a search layer, not an agent. The company is investing heavily in AI, but the investments are in making search better, not in building transactional AI capabilities.

The Common Thread: All Three Are Building Better Search, Not Agents

Here's the pattern that emerges across all three companies:

Capability	Expedia	Booking	Trip.com
Natural language search	Yes	Partial	Yes
AI recommendations	Yes	Yes	Yes
Itinerary planning	Partial	Partial	Yes
Transactional booking	No	No	No
Multi-step execution	No	No	No
Third-party agent integration	No	No	No

All three can search. All three can recommend. None can execute. None can handle multi-step tasks. None are building infrastructure for third-party AI agents.

This is the core of the "theater" accusation. These companies are spending hundreds of millions on AI, but they're spending it on making their existing search product slightly better. They're not spending it on the thing that actually threatens their business: transactional AI agents that can book travel without opening an OTA app or website.

Why It's Theater: The Incentive Problem

Why would three of the smartest companies in travel spend hundreds of millions on AI that doesn't address the core threat? Because of incentives.

A transactional AI agent that books hotels directly — bypassing the OTA website — would destroy the OTA's business model. OTAs make money by controlling the booking flow: sponsored placements, cross-sell opportunities, advertising, and the 15–25% commission on every booking. If users book through an AI agent that connects directly to hotel inventory, the OTA is cut out of the loop entirely.

So OTAs face an innovator's dilemma: building a true transactional AI agent would cannibalize their existing business. Not building one means third-party agents will do it for them, and the OTA becomes irrelevant.

Their solution? Build AI that looks impressive in demos and earnings calls but doesn't actually threaten the core business. A conversational search interface. An itinerary planner. A review summarizer. These are "AI features" that generate headlines and investor confidence without disrupting the revenue engine.

It's not that these companies are stupid or short-sighted. It's that the incentives are structurally aligned against building the thing that needs to be built. The CEO who says "we're going to build an AI agent that bypasses our own website" would be fired by the board. The CEO who says "we're investing $500 million in AI to enhance our customer experience" gets a bonus.

What a Real AI Travel Strategy Would Look Like

If I were running one of these companies and wanted to actually prepare for the agentic future, here's what I'd do:

Launch an MCP-compatible inventory server. Open up hotel inventory to third-party AI agents through a standard protocol. Yes, this cannibalizes direct website bookings — but if I don't do it, someone else will, and I'll be cut out entirely. Better to own the infrastructure than to be bypassed by it.
Build a transactional AI agent that works across platforms. Not just inside my app, but as an MCP server that any AI client can use. Let users book through Claude, ChatGPT, or any other agent — with my company handling the inventory, payment, and customer service behind the scenes.
Transition from commission to infrastructure revenue. Instead of making 15–25% on every booking through my website, make 2–5% on every booking through my infrastructure, at 10x the volume. Lower margin per booking, but much higher total volume and much lower customer acquisition cost.
Leverage trust and customer service as the differentiator. AI agents are unreliable. My company has 20+ years of trust, customer service infrastructure, and dispute resolution. Position my company as the "reliable backend" for AI travel booking — the infrastructure that agents use when they need to get it right.

This is a bold strategy that requires accepting short-term pain for long-term survival. It's also the strategy that none of the three OTAs are pursuing, because it requires cannibalizing the existing business.

But someone is pursuing it. RollingGo Hotel MCP is building exactly the infrastructure the OTAs refuse to build: a standardized MCP endpoint that gives any AI agent access to 2 million+ hotels from 500+ suppliers, with real-time pricing, three production tools (searchHotels, getHotelDetail, getHotelSearchTags), and free unlimited API keys. The connection is one JSON block:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer mcp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

This isn't a demo. It isn't a pilot. It's production infrastructure that 2,500+ agents and applications already use. Every searchHotels call returns live prices from inventory. Every result includes a bookingUrl that completes the transaction. The OTAs are spending hundreds of millions on AI that doesn't threaten their core business. RollingGo is spending engineering effort on infrastructure that does.

The Bottom Line

The AI strategies of Expedia, Booking Holdings, and Trip.com are real in the sense that they're spending real money and building real features. But they're theater in the sense that the features don't address the fundamental disruption facing the industry. They're building better search when the future is transactional agents. They're enhancing the website when users are leaving the website. They're optimizing the old model while the new model is being built around them.

I'm not saying these companies will fail. They have enormous resources, strong brands, and deep supplier relationships. But I am saying that their AI strategies are defensive, not offensive. They're designed to protect the existing business, not to win the future.

The companies that win the AI travel era won't be the ones with the best search AI. They'll be the ones with the best transactional infrastructure — the MCP servers, the booking APIs, the payment systems, and the customer service that AI agents rely on to actually get things done.

The OTAs are performing AI. Someone else is building it.

The MCP infrastructure that OTAs aren't building — but AI agents actually need — is available as open-source software: RollingGo Hotel MCP on GitHub.

Every AI Travel App Is Losing Money. The People Building MCP Infrastructure Are Already Profitable.

Becky_dev — Tue, 13 Oct 2026 13:20:00 +0000

Here's a fact that should make every AI travel startup founder uncomfortable: there are dozens of AI travel apps on the market, and almost none of them are profitable. Meanwhile, the companies building MCP infrastructure — the boring, unsexy, behind-the-scenes tools that power AI travel booking — are already generating revenue.

This isn't a coincidence. It's a structural pattern. And if you're building or investing in AI travel, you need to understand it, because it determines who wins and who loses in this market.

Let me break it down.

The AI Travel App Graveyard: Where the Money Goes

Take a quick tour of the AI travel app landscape. There are apps that plan itineraries. Apps that find flight deals. Apps that book hotels through chat. Apps that act as "travel concierges." Apps that generate packing lists. Apps that translate foreign languages. Apps that do all of the above.

Most of them have raised seed or Series A funding. Most have impressive user growth numbers. Almost none are profitable. Here's why:

Customer acquisition cost (CAC) is brutal. The travel market is dominated by OTAs that spend billions on marketing. Booking.com alone spent over $5 billion on marketing in 2024. An AI travel startup trying to acquire users is competing with companies that can outspend them 100-to-1. The average CAC for a travel app user is $30–$80. For a user who might book one $200 hotel room per year, generating $20 in commission, the math doesn't work.

Retention is terrible. People don't travel every day. They book a trip, use the app for a week, and then don't open it again for 6–12 months. By the time they travel again, they've forgotten the app exists, or they've seen an ad for a competitor. Monthly active users (MAU) spike around booking periods and crash in between.

Monetization is indirect. Most AI travel apps make money through affiliate commissions — they send users to OTAs and get a cut of the booking. This means they're not really a travel business; they're a marketing channel for OTAs. And OTAs know it — they can change commission rates, reduce cookie windows, or launch competing products at any time. The app's revenue is entirely dependent on the goodwill of companies that see them as either customers or threats.

The AI isn't defensible. Every AI travel app uses the same underlying models (GPT, Claude, Gemini) and the same inventory sources (OTA APIs). The "AI" in "AI travel app" is a thin layer on top of commoditized infrastructure. There's no moat. A competitor can build the same app in a weekend.

Put it all together: high CAC, low retention, indirect monetization, no moat. This is a recipe for burning investor money until the funding runs out. And that's exactly what's happening.

The MCP Money Machine: Where the Profit Is

Now look at the other side of the market: MCP infrastructure. These are the companies building the servers, protocols, and tools that let AI agents connect to real-world services like hotel booking. They're not building consumer apps. They're building the pipes.

And they're making money. Here's why:

Customers are developers and businesses, not consumers. MCP infrastructure companies sell to developers who build AI agents, and to businesses that want their services accessible through AI. These customers have budgets, make purchasing decisions rationally, and don't require Super Bowl ads to acquire. CAC is a fraction of consumer app CAC.

Revenue is recurring and transaction-based. MCP servers charge either a monthly subscription, a per-transaction fee, or a freemium model with paid tiers. Every time an AI agent books a hotel through the MCP server, the server generates revenue. This is direct monetization — no affiliate links, no cookie windows, no dependence on OTA goodwill.

Retention is structural. Once a developer integrates an MCP server into their AI agent, switching costs are high. The agent is built around the MCP server's tools, data formats, and APIs. Moving to a competitor requires rewriting integration code, retesting, and risking breakage. Developers stay. Businesses stay. Revenue compounds.

The infrastructure is the moat. A hotel MCP server that has real-time inventory from 2 million+ hotels, reliable pricing APIs, and customer support is not something a competitor can build in a weekend. It requires supplier relationships, technical infrastructure, compliance certifications, and operational scale. This is a real moat.

RollingGo is the case study. It aggregates 2 million+ hotels from 500+ suppliers across 200+ countries, including 110,000+ directly contracted properties. Its v1.0 exposes three tools (searchHotels, getHotelDetail, getHotelSearchTags) through a single MCP endpoint. The business model is deliberately counterintuitive: API keys are free, calls are unlimited, approval is instant. No credit card required. No rate limits. No per-query fees.

How does that make money? Four identity tiers capture value at different levels:

Personal — free, for individual AI tool users (builds ecosystem adoption)
Developer — free, with Partner Center access for traffic analytics (locks in integration)
KOL/Affiliate — free, with tracked bookingUrl links that earn commission on every completed booking (revenue share without infrastructure cost)
Enterprise — paid, with team management, budget controls, audit trails, and volume pricing (the real revenue engine)

The free tier isn't a charity — it's a distribution strategy. Every developer who connects RollingGo to their agent is another distribution channel. Every KOL who uses the affiliate link is another salesperson. The enterprise tier captures the value when those channels scale. This is the AWS playbook: give away the infrastructure to developers, then monetize the enterprise demand that follows.

The connection takes five minutes:

{
  "mcpServers": {
    "RollingGo-Hotel": {
      "url": "https://mcp.rollinggo.ai/mcp",
      "type": "streamable-http",
      "headers": {
        "Authorization": "Bearer mcp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The result: MCP infrastructure companies have low CAC, high retention, direct monetization, and real moats. They're profitable or on a clear path to profitability. Meanwhile, AI travel apps burn cash chasing consumers who don't come back.

The Numbers: A Side-by-Side Comparison

Let me make this concrete with a hypothetical but realistic comparison:

Metric	AI Travel App	MCP Infrastructure
Customer type	Consumer traveler	Developer / business
CAC	$40	$200 (but 1 customer = 1000s of end users)
Retention (12-month)	15%	85%
Revenue per customer	$20/year (affiliate)	$1,200/year (subscription + transactions)
LTV:CAC	0.75:1 (losing money)	5:1 (profitable)
Time to profitability	36+ months (if ever)	12–18 months
Moat	None	Inventory + relationships + scale

The AI travel app spends $40 to acquire a user who generates $20 in lifetime revenue. It loses $20 per user. The MCP infrastructure company spends $200 to acquire a developer who generates $1,200 in annual recurring revenue. It makes $1,000 per customer per year, and that customer stays for years.

This isn't a close call. The infrastructure business is fundamentally better.

Why This Pattern Keeps Repeating

This isn't the first time we've seen this pattern. In every major technology shift, the companies that make money are the ones that build infrastructure, not the ones that build consumer applications on top of it:

Gold rush: Levi Strauss sold jeans to prospectors. The prospectors mostly went broke. Levi Strauss became wealthy.
Internet boom: Cisco sold routers. Akamai sold CDN. AWS sold cloud computing. The consumer apps built on top of them (Pets.com, Webvan) went bankrupt. The infrastructure companies thrived.
Mobile boom: Apple sold iPhones. Google sold Android. App developers made pennies. The platform owners made billions.
AI boom: NVIDIA sells GPUs. OpenAI sells models. MCP servers sell infrastructure. The AI apps built on top are fighting for scraps.

The pattern is clear and consistent: in a technology gold rush, sell picks and shovels. Don't dig for gold.

In AI travel, the "picks and shovels" are MCP infrastructure — the servers, protocols, and tools that let AI agents connect to real travel inventory and complete bookings. The "gold" is the consumer travel booking, which everyone is chasing and almost no one is capturing profitably.

What This Means for Founders and Investors

If you're a founder building an AI travel app, you have three options:

Option 1: Keep building the app and hope for the best. Maybe you'll be the one consumer app that breaks through. The odds are against you, but it's possible. You'll need a huge marketing budget, a viral growth loop, or a unique value proposition that no one can copy. Most apps don't have any of these.

Option 2: Pivot to infrastructure. Stop building a consumer app and start building the infrastructure that powers AI travel. This is harder technically but easier commercially. You'll sell to developers and businesses, not consumers. You'll have recurring revenue, high retention, and a real moat. This is the path that's already generating profit.

Option 3: Hybrid model. Build a consumer app that's powered by your own MCP infrastructure. The app is a demonstration of the infrastructure's capabilities (and a source of direct booking revenue), while the infrastructure is sold to other developers and businesses. This is the AWS model — Amazon built AWS to power its own retail business, then sold it to everyone else.

If you're an investor, the math is simple: infrastructure investments have better risk-adjusted returns than consumer app investments. You're not betting on a single app's viral growth. You're betting on a structural shift in how AI agents connect to real-world services. That shift is happening regardless of which consumer app wins.

The Counterargument: "But Someone Has to Build the Apps!"

I know what you're thinking. "If everyone builds infrastructure and no one builds apps, there's no demand for the infrastructure." And you're right — there needs to be a healthy ecosystem of AI travel apps to drive demand for MCP infrastructure.

But here's the thing: the apps will be built. They'll be built by thousands of developers, small teams, and niche players. They won't be giant, venture-backed consumer apps. They'll be specialized agents — a ski trip planner, a business travel optimizer, a family vacation coordinator — each serving a specific niche. These apps will be profitable at small scale because they have low CAC (niche targeting) and high retention (serving a specific use case).

The infrastructure providers will serve all of them. That's the beauty of the infrastructure model: you don't need to bet on which app wins. You win regardless, because every app needs your infrastructure.

The Bottom Line

The AI travel market is undergoing a massive shift. Consumer-facing AI travel apps are burning investor money with no clear path to profitability. MCP infrastructure companies are generating real revenue with strong unit economics. The pattern is as old as technology shifts: infrastructure wins, applications fight for scraps.

If you're building in this space, ask yourself: am I selling picks and shovels, or am I digging for gold? The answer determines whether you'll be profitable in 18 months or out of business in 36.

The gold rush is on. Everyone's chasing the consumer. The smart money is building the rails.

The hotel MCP infrastructure that's powering the next generation of AI travel apps is open-source and free to start using: RollingGo Hotel MCP on GitHub.

DEV Community: Becky_dev

The Next Travel Search Engine Might Be a Conversation. The Hard Part Is What Happens Next

1. Travel Discovery Is Moving Into the AI Conversation

2. The Real Bottleneck Isn't Intelligence. It's Access.

3. Why MCP Matters for AI Travel Developers

4. Building the Connection Between AI and Real Hotel Options

5. The Next Travel Interface May Not Look Like a Travel Interface

6. What Developers Should Build for Next

Make travel data actionable

Design for changing information

Keep the path to booking clear

7. From AI That Talks About Travel to AI That Helps Make It Happen

Build with RollingGo Hotel MCP

AITravel #TravelTech #AIAgents #MCP #AgenticAI #HotelTech #TravelDevelopers

The Next Hotel Search Box May Not Look Like a Search Box: How RollingGo Hotel MCP Connects AI to Real Travel Supply

1. Hotel Discovery Is Moving Beyond Traditional Search

2. Cloudbeds and Meta Muse Highlight a Bigger Industry Shift

3. The Missing Layer Between AI Conversations and Hotel Inventory

4. RollingGo Hotel MCP: Connecting AI to Real Hotel Search

5. From Hotel Search to Agentic Commerce

6. Why Travel Developers Should Think About Connectivity Now

7. The Future of Hotel Search Is About What Happens Next

The Next Travel Revolution Won't Happen Inside Another Booking App

The interface is changing — but the underlying work remains

What is agentic commerce in travel?

Why travel needs an infrastructure layer for AI

RollingGo: connecting AI agents with hotel capabilities

From a single booking funnel to connected services

What travel startups and developers can build

The business question: who owns the experience?

What must happen before agentic travel becomes dependable?

The next booking interface may be a conversation

RollingGo #AgenticCommerce #AITravel #TravelTech #MCP #HotelBooking #AIAgents

From NVIDIA RTX Spark to AI Travel Agents: Why Real-World Data Matters More Than Ever

1. NVIDIA RTX Spark and the Rise of Personal AI Agents

2. Why AI Travel Agents Need More Than a Language Model

3. What Is MCP, and Why Does It Matter for AI Agents?

4. Introducing RollingGo Hotel MCP

What can developers build with RollingGo Hotel MCP?

5. From Hotel Recommendations to Actionable Travel Workflows

6. Why Local AI and Travel MCP Are Complementary

7. How to Get Started with RollingGo Hotel MCP

8. The Future of AI Travel Is About Connecting Capabilities

Frequently Asked Questions

What is RollingGo Hotel MCP?

How does MCP help AI travel agents?

Can an AI agent search real hotel availability?

Does RollingGo Hotel MCP work only with NVIDIA RTX Spark PCs?

Who should use RollingGo Hotel MCP?

Where can developers learn more?

Further Reading

The Endgame of AI Travel: Super App or Super Agent? I'm Betting Everything on Agent.

Defining the Two Visions

Why the Super App Model Is Doomed

Why the Super Agent Model Is Inevitable

The Timeline: When This Happens

What This Means for Different Players

The Counterargument (and Why It's Wrong)

The Bottom Line

Behind the Free API Key: Why We Dare to Offer Unlimited MCP Calls

The Traditional API Pricing Model (and Why It's Broken for AI)

The Business Model: Free Keys, Transaction Revenue

The Numbers: Why Free Keys Are Cheaper Than Paid Acquisition

The Scale Effect: Why Marginal Cost Approaches Zero

What Competitors Don't Understand

The Risks (and How We Manage Them)

The Bigger Bet: AI Infrastructure Will Be Free

Stop Learning Prompt Engineering. The Future Belongs to Tool Engineering

Why Prompt Engineering Is Dying

What Is Tool Engineering?

The Skill Comparison: Prompt Engineering vs. Tool Engineering

Why MCP Is the Foundation of Tool Engineering

How to Make the Switch

The Market Reality

AI Booking Hallucinations Are Costing Travelers Real Money. Here's the Proof.

The Four Types of AI Booking Hallucinations

Type 1: The Phantom Hotel (19 cases, average loss: $87)

Type 2: The Price Hallucination (14 cases, average loss: $142)

Type 3: The Amenity/Policy Fabrication (9 cases, average loss: $213)

Type 4: The Booking Confirmation That Never Happened (5 cases, average loss: $340)