Mashup

The term comes from music. There, a mashup refers to a song assembled from parts of two other songs. In the software world, the word means something very similar. A mashup is a service that brings together content or functions from multiple external providers and turns them into something new. The provider of the mashup usually hasn’t collected the data itself. Its contribution is the combination: it connects building blocks that previously had nothing to do with each other. The best-known example is a real estate site that takes apartment listings from a database and plots them on a map from Google.

Why nobody reinvents the map

Creating a worldwide street map costs billions. A weather service needs measuring stations, satellites, and meteorologists. A small company can’t afford that. But it can buy these services or use them for free and build them into its own product. This creates services that simply wouldn’t otherwise exist.

Economically, this shifts the question of where a product’s value lies. Here, the data itself is not the capital, but the meaningful linkage. An app that brings together timetables, rental bikes, and weather owns not a single bus. Yet it can be more valuable to users than any of the three individual sources. This exact logic shaped many web services starting around 2005.

There is a tangible downside. Anyone who builds on external sources becomes dependent on them. If the provider changes its prices, its rules, or discontinues the service, the mashup grinds to a halt. Several well-known map and Twitter mashups failed for exactly this reason, when usage suddenly started costing money.

The interface as a power outlet

Technically, mashups hang off so-called interfaces, usually called APIs. An interface is a defined way for one program to ask another for data. You can think of it like a power outlet: the shape is standardized, so every plug fits. The mashup sends a request, say an address, and gets back a structured response, say latitude and longitude.

The response doesn’t arrive as a finished web page, but as pure data structure. The common format is JSON, a simple list of field names and values. The mashup reads out these values and decides for itself how to display them. Often part of this happens directly in the user’s browser, another part on the provider’s server.

A common misconception is that a mashup is the same as an integration or a plugin. The difference lies in the direction. A plugin extends an existing program with a function. A mashup, by contrast, is a standalone product that merges multiple equal-standing sources. And it typically uses these sources in a way their operators had not planned for at all.

From the delivery app to the AI agent

In everyday life, people constantly use mashups without knowing the word. A delivery app shows the map from one provider, handles payment through a second, and sends notifications through a third. Price comparison sites query dozens of shops simultaneously. Fitness apps that overlay weather data on your running route also belong to this category.

The term appears less often in the news today than around 2008, but the principle is more important than ever. When a chatbot searches the web, books a flight, and adds an appointment to a calendar, it is at its core a mashup with voice control. Such systems are called AI agents. They access external services through the very same interfaces.

That’s why it’s worth paying attention to the interface policies of major platforms. Whoever raises the price of access or shuts it down also decides which new products can come into existence at all. That is precisely why news about changed API pricing matters to the entire industry.