News your agent can actually use
One event returns once, with the outlets that covered it. Query by meaning, filter by language and publisher, and call it from your backend or straight from Claude.
1,000 credits a month, free forever. No card required.
Provisional figures, regenerated each publication cycle from the source the index is built on.
Twenty results, one story
A wire report reaches hundreds of sites within an hour. Search for it and you get all of them back, each ranked as an independent result. A person skims past the repetition. A model reads the same fact twenty times, fills its context, and treats the repetition as corroboration.
Ask for stories instead of articles and that event arrives once, carrying the list of publishers who ran it. Three outlets or thirty — that number tells you more than the article count ever did.
Built for tool calls
A first-party MCP server
Eighteen tools over the same query surface as the REST API, with the same filters and the same key. No community wrapper to maintain, no drift between what your backend does and what your agent does.
Matching on meaning
A layoff is also a restructuring, a headcount reduction and letting people go. Keyword search finds whichever phrasing you guessed. Semantic and hybrid modes find the event.
26 languages, filtered properly
Japanese has no spaces. Arabic drops its vowels. Serbian is written in two alphabets at once. Language is a first-class filter here, not a flag bolted onto an English index.
Nothing gated
Semantic retrieval, story grouping and MCP access are on the free tier. Paid plans buy credits, history and credits a minute. You evaluate what you would ship.
Start here
Called from an agent
What we return
Headline, publisher, timestamp, language, link, and a story identifier. Not article bodies — those stay with the publishers who wrote them, and you stay clear of the licensing questions that follow full text around.
Small responses suit agents well. A model choosing what to read next needs to compare candidates, not consume them, and a compact result set lets it weigh far more options for the same budget. When one of them matters, its story identifier expands into the whole story in one call: every article, every outlet, first and last seen. Filters are exact, so a name resolves first to the spellings the index holds, grouped with counts. Other filters take a radius around a point or a class of event, such as a bankruptcy or a strike. The resolved id also shows who is reported alongside it, with the articles behind every connection.
Where this is the wrong choice
If your application needs the full text of articles, this is not the foundation for it and no plan changes that — license text from the publishers directly. If your reader is a person scanning a feed and duplicate coverage does not bother them, simpler and cheaper options exist and the grouping you are paying attention to here is solving a problem you do not have. If you need newspaper front pages, or country filtering as the primary axis of your product today, other vendors are genuinely stronger and the comparison pages say which and why. And if you have a regulatory screening obligation, buy a screening vendor: this is a news index, with no list coverage, no resolution against a registry and none of the audit guarantees that obligation carries.
The general shape of the limit is worth stating once. A news index tells you what is being reported, which is narrower than it sounds — it is silent on what is true, on what is planned, and on everything that happened without anyone writing about it. It is a timeliness instrument rather than a completeness one, and most disappointment with this category comes from buying it as the second thing. Each solution page names the limit for its own job, which is usually the part that decides whether it fits.