Every search box is a survey. People type what they actually need, in their own words, and they do it whether or not the thing they’re after exists yet. So once a day we roll up the apisearch events coming off the search and MCP server and read them as a demand signal. Here’s what that signal looked like across the last three days on apis.io — 3,941 searches, 1,761 distinct queries, and a spread of topics wide enough to be worth pausing on.
The shape of a day
Today alone (2026-06-22) saw 1,479 searches resolving to 713 distinct queries. Yesterday was busier still — 2,362 searches, a full thousand distinct queries. Nearly all of it is internal: people using the search box on apis.io itself, not anonymous API or MCP callers. That matters, because it means these are humans on the site trying to find something, not bots crawling it.
The range is the story
What stands out isn’t any single query — it’s how little the top terms cluster. A catalog of 10,000+ providers gets searched like a switchboard for the whole API economy. The top of the list this window:
| Query | Hits | What they’re really after |
|---|---|---|
payments |
16 | The perennial #1 — money movement is still the gateway drug to APIs |
vehicle / vehicle united kingdom |
16 | Mobility and automotive data, geo-scoped |
Image Repository |
10 | Media/asset storage and delivery |
postcode |
8 | Location and address resolution |
Education |
8 | A whole vertical, searched as one word |
weather |
6 | Climate and forecast data |
Congestion |
6 | Traffic and transit telemetry |
RAG |
6 | Retrieval-augmented generation — AI tooling |
Card on File |
4 | Back to payments, but a precise primitive |
Fault Injection |
4 | Chaos engineering and resilience testing |
TLSInspection |
4 | Network security |
Publish Subscribe |
4 | Event-driven architecture |
Read that column top to bottom: fintech, automotive, media, geodata, education, climate, mobility, AI, devops resilience, security, and eventing — eleven different worlds in a dozen rows. Nobody designed that diversity. It’s just what people need on a Monday.
The most interesting list is the one that returned nothing
Of today’s 713 distinct queries, 274 came back empty — and across the window there were 701 distinct zero-result searches. That’s not a failure mode; it’s the most honest roadmap we have. People are telling us, in plain language, what they expected the catalog to contain and didn’t find:
OpenAI Compatible— the new lingua franca; people want APIs that speak the OpenAI wire format.Document ExtractionandReal World Data— the AI-meets-healthcare/ops frontier.Commodity Insights,Industry Data,Financial Standards— structured market and reference data.Goods Delivery,Vendor Management,Service Catalog— the unglamorous plumbing of running a business.Real-time Streaming,Publish Subscribe,Network Query— event and streaming surfaces.Irradiance Modeling— solar and energy modeling, a single specialist crying out into the void.
Each of these is a small vote for what apis.io should index next. When a query like OpenAI Compatible or Document Extraction shows up repeatedly and returns nothing, that’s not noise — that’s a backlog item with a built-in demand estimate.
Why we publish this
A catalog is only as good as the questions it can answer. Reading search demand out loud does two things: it keeps us honest about the gaps, and it shows the rest of you the texture of what people are actually looking for — which is often more useful than any “top APIs of 2026” listicle. The API economy isn’t a handful of categories. It’s payments and postcodes and irradiance modeling, all in the same afternoon.
Where to start
- Search apis.io — add your own query to tomorrow’s report.
- Browse industries — the verticals behind terms like
Educationandweather. - Provider profiles — where a search like
paymentsactually lands. - The MCP server catalog — for the agents doing this searching programmatically.
If you searched for something this week and came up empty, you were heard. The zero-result list is where the next hundred providers come from.