Home / Languages / Chinese

Chinese news API

Query 中文 coverage by keyword, meaning or both. Written in Han (Simplified and Traditional) . Pass zho as the language filter.

What the coverage looks like

A stream covering mainland, Hong Kong, Taiwan and diaspora publishers whose framing of the same event differs substantially. Business, technology and trade coverage is dense; the mix of publisher origins matters more for interpretation than the raw volume does.

Articles observed6.4k
Distinct outlets159
Articles per outlet40
ISO-639-3 codezho
ScriptHan (Simplified and Traditional)

Outlet spread is the number worth watching here, not volume. 159 distinct publishers at roughly 40 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 china.com, carrying about 9% of Chinese articles on its own, and the three busiest — china.com, 163.com, baidu.com — account for roughly 23% 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

Written without spaces between words, so there is no boundary for a keyword matcher to split on and token segmentation has to be inferred. Simplified and Traditional characters both circulate and do not match each other, so a query in one script silently misses coverage in the other.

How to query it

Semantic mode by default. Where you must use keyword mode, account for both character sets. Outlet scoping is essential if publisher origin matters to your analysis, which for most purposes it does.

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 Chinese

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.

china.com · 163.com · baidu.com · cfi.net.cn · sina.com.cn · udn.com · cna.com.tw · ltn.com.tw · setn.com · itbear.com.cn · ettoday.net · zol.com.cn

What catches people out

The character-set split is the mechanical trap and publisher origin is the analytical one. Simplified and Traditional characters do not match each other, so a query in one silently misses coverage in the other; and mainland, Hong Kong and Taiwan publishers frame the same event differently enough that an unscoped query blends incompatible perspectives.

A worked case

Account for both character sets, and scope by outlet whenever framing matters. For supply chain and manufacturing stories, Chinese-language coverage regularly carries specifics — named facilities, revised volumes, supplier relationships — that reach English reporting days later in compressed form, if at all.

Where this language leads

Very strong on manufacturing, trade, technology supply chains and regional economics, frequently with specifics that reach English-language coverage days later if at all.

Who queries it, and why

Queried for manufacturing, trade and technology supply chains, where the specificity available domestically has no English equivalent and the lead time is measured in days. Publisher origin matters enough that ignoring it produces analysis that averages incompatible framings.

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 Chinese 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.