Russian news API
Query Русский coverage by keyword, meaning or both. Written in Cyrillic . Pass rus as the language filter.
What the coverage looks like
A large stream spanning Russia and Russian-language outlets across the former Soviet space, with editorial positions that differ sharply depending on where a publisher is based. Treating all Russian-language coverage as one perspective is the most common analytical mistake made with this language. The stream is large enough that unscoped queries almost always return something plausible, which is precisely what makes it risky: plausibility here is not evidence of representativeness. Coverage of the same event from publishers in different jurisdictions can differ not only in framing but in which facts are reported at all, so a result set that looks internally consistent may simply reflect a single editorial position reached by an unscoped query.
| Articles observed | 4.3k |
|---|---|
| Distinct outlets | 296 |
| Articles per outlet | 14 |
| ISO-639-3 code | rus |
| Script | Cyrillic |
Outlet spread is the number worth watching here, not volume. 296 distinct publishers at roughly 14 articles each describes a very different information environment than the same total produced by a handful of prolific sources — and it is the difference between reaching independent reporting and reading one newsroom repeatedly.
In this sample the most active publisher is rg.ru, carrying
about 4% of Russian articles on its own, and the three busiest
— rg.ru, lenta.ru, news.mail.ru — account for roughly 10% between
them. That is a comparatively flat distribution, which means volume here translates fairly directly into independent reporting rather than one newsroom publishing repeatedly.
Script and matching behaviour
Cyrillic script and six cases, with stem changes as well as suffix changes. Word order is flexible, so phrase-based matching is unreliable in a way it is not in English. Names of foreign people and organisations are transliterated with genuine variation between outlets.
How to query it
Semantic mode, always, and scope by outlet if the editorial position of the source matters to your analysis — which for this language it usually does. Entity filters are more reliable than name strings for foreign proper nouns.
Bound every request with a time range regardless of mode. Meaning-based retrieval always returns its best guesses, so an unbounded query produces a confident-looking result set anchored to nothing in particular. If results feed a model rather than a person, collapse to stories as well — one event covered by thirty outlets should cost you one item, not thirty.
Recent headlines in Русский
Pulled from the index on 2026-07-31, shown in their original script so you can see what the API actually returns rather than a translated approximation of it.
Outlets publishing in Russian
The most active publishers in this language, by article count. Use these as an outlet filter when you want to pin a particular market or editorial position rather than taking the whole language.
rg.ru · lenta.ru · news.mail.ru · ria.ru · vesti.ru · vz.ru · life.ru · m24.ru · 1prime.ru · rt.com · 24tv.ua · aif.ru
What catches people out
Treating all Russian-language coverage as one perspective is the significant analytical error, and it is common. Publishers based in different countries take sharply different editorial positions, and a query that does not distinguish them produces a stream whose apparent consensus is an artefact of which outlets it reached.
A worked case
Scope by outlet whenever editorial position matters, which for this language is most of the time. Use entity filters rather than name strings for foreign people and organisations, since transliteration varies between publishers and a single spelling captures an unpredictable fraction of the coverage.
Where this language leads
Extensive on domestic and regional politics, energy markets and defence. Coverage of Central Asia and the Caucasus is far deeper than anything available in English.
Who queries it, and why
Queried for regional politics, energy and defence, and for Central Asian and Caucasus coverage that has no English-language equivalent. The editorial-position problem makes outlet scoping not merely advisable here but a precondition for the results meaning anything.
Reading these numbers
These figures are provisional. They are measured from the public source the index is built from rather than from the index itself, because the query endpoint is not yet reachable from the build. They are the right order of magnitude and the outlets and headlines are real, but they should not be quoted as coverage guarantees until a snapshot taken against the API replaces them.
A page exists for this language because the index carries enough Russian coverage from enough distinct outlets to answer a real question about it. Languages that do not clear that bar deliberately have no page rather than a page that implies coverage which is not there.