REST + MCP

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 requests a month, free forever. No card required.

26languages covered
78karticles indexed
169publishers
6MCP tools

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.

40 articles one wire report, republished group covered by +34 1 story with every outlet that ran it
A busy news day, before and after grouping. The outlet list replaces the duplicates.

How story grouping works →

Built for tool calls

Start here

Called from an agent

agent Claude · ChatGPT list_stories 8 events MCP 6 tools same key as REST index grouped
The MCP server exposes the same six operations as the REST API, authenticated with the same key.

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.