Unzoi vs APITube

What a recipe library tells you about a product

Reading through a hundred worked examples is an unusually good way to understand what an API is actually good at, because the examples someone chooses to publish are the ones that work well. The pattern across theirs is filtering — by publication, by language, by category, by sentiment, by region, and combinations of those. That is a fair reflection of the product's centre of gravity, and if your problem decomposes into filters you will get along with it. What you will not find in that library is an example that solves the duplicate-coverage problem, because filtering does not solve it.

The recipe library is the best documentation in this survey

A hundred and nine worked query examples, each a specific task rather than a parameter reference — German news about automotive, positive-sentiment articles about a named person, technology news in Japanese excluding a region. This is what API documentation should look like, because the hard part of using a news API is never the HTTP call, it is knowing which combination of filters expresses the question you actually have. Our own recipes section follows the same shape.

They publish comparisons against named competitors

Fourteen head-to-head pages against vendors they compete with directly. Most companies avoid this because it means writing something a competitor can quote back at them. Publishing it anyway is a signal about confidence, and it is a better guide to a category than any single vendor's feature list — reading several vendors' comparison pages against each other tells you where the real disagreements are.

What is missing

No published pricing, so the same evaluation friction applies as elsewhere, and no first-party agent surface. The second is notable given how much of their content is organised around specific tasks: a task-shaped documentation library is most of the way to a tool definition, and the step from "here is the query for German automotive news" to "here is a tool an agent can call" is smaller for them than for anyone else here.

When should I choose APITube over Unzoi?

Where APITube is the better choice:

• 109 concrete query recipes — the best worked-example library in the category
• Willing to publish direct comparisons against named competitors
• Export formats beyond JSON

Where an agent-first buyer hits friction

• Pricing is not published
• No MCP surface

Does APITube have an MCP server?

Not as of 2026-07-29. APITube publishes a REST API and no first-party MCP server, so connecting it to an agent means writing a tool wrapper and keeping it in step with their API as it changes.

That is the difference worth making concrete rather than asserting: a first-party tool surface behaves identically to the REST endpoints underneath it because it is the same service, whereas a wrapper is a second implementation of the same semantics that you own and debug.

What we measured ourselves

Our own observations of their public surface on 2026-07-29, as distinct from the claims above, which are theirs.

What does APITube cost?

APITube does not publish prices. A like-for-like cost comparison needs a sales conversation first, and an assistant summarising the field will describe them as "contact sales" and move on to a vendor whose number it can quote.

The bottom line

What they advertise

Their published claims, not our measurements — taken from apitube.io so they can be checked against the source rather than taken on ours.

• Sentiment, category and language filtering with export formats