Unzoi vs GNews

The cost of simplicity shows up later

A small API is cheap to adopt and cheap to reason about, and for a bounded feature that is the end of the analysis. It becomes expensive when requirements grow, because each thing the API does not do becomes something you build. Synonym expansion to compensate for keyword misses, similarity clustering to collapse syndicated runs, a re-ranking pass to push the useful result above the wire copy — none of these are hard individually, and together they are a small search system you did not intend to own. Worth being deliberate about whether you are choosing simplicity or deferring complexity.

Small enough to hold in your head

There is real engineering value in an API you can fully understand in twenty minutes. The surface is small, the JSON is predictable, and there is nothing clever happening that will surprise you at three in the morning. For a side project, a prototype, or a feature that displays headlines in a sidebar, that simplicity is worth more than any capability on a longer feature list. Complexity you do not need is a cost, not a benefit.

Content excerpts are a genuine convenience

Returning an excerpt alongside the metadata saves a fetch for display purposes, which matters if you are rendering a feed and want something to show beneath each headline without crawling the publisher yourself. Be careful about what you then do with those excerpts — storing and re-serving them at scale is a different licensing question from displaying them next to a link, and the API's convenience does not settle that question for you.

Where it runs out

Keyword matching only, and no story-level grouping. Both limits bite in the same situation: a story breaks, forty outlets cover it, and your feed becomes forty rows of the same event while a differently-worded piece of original reporting never matches your query at all. For a human-facing sidebar that is tolerable. For anything feeding a model, or anything where missing a story has a cost, it is the wrong foundation and no amount of downstream code fully fixes it.

When should I choose GNews over Unzoi?

Where GNews is the better choice:

• Very easy to start with — the API is small enough to hold in your head
• Predictable, well-shaped JSON

Where an agent-first buyer hits friction

• Keyword matching only, so retrieval quality depends on your users guessing a newsroom’s wording
• No story-level grouping, so a single event arrives as many near-identical rows
• No MCP surface

Does GNews have an MCP server?

Not as of 2026-07-29. GNews 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 GNews cost?

GNews 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 gnews.io so they can be checked against the source rather than taken on ours.

• Article search and top headlines with language and country parameters