The same pipeline that publishes the Zaviye newsroom is exposed as a commercial API. Farsi, Kurdish, Arabic, Turkish, and English-language press — ingested, clustered by embedding similarity, cross-language-matched, framing-annotated, and served as JSON. REST and MCP interfaces. Free, self-serve. No sales calls.
227 feeds across 8 languages, indexed as first-class corpora — not an afterthought. Most commercial news APIs offer English-only or bolt-on translation of English sources.
02
Cross-language clustering
Clusters are matched across corpora by embedding similarity. A story that ran in Kurdish and Turkish but not English is one cluster with three language slots, not three separate records.
03
Framing + bias annotations
Per-cluster framing analysis in each corpus, source-spectrum breakdown, state-media flags. The analysis layer runs on every cluster by default, free.
04
Coverage-gap signals
Endpoints that return clusters with high inter-corpus disparity — the stories one side filled pages on and another barely touched. A sellable primitive for media-monitoring products.
05
MCP + REST from the same data
Build a Claude integration with the MCP server today; move to REST for production traffic; same cluster store, same account, same rate bucket.
06
Same data the Zaviye newsroom publishes
No separate pipeline, no separate quality tier. What the API returns is what readers see on zaviye.news.
One tier, everything included — the full five-language cluster access, framing analysis, source-bias breakdowns, and coverage-gap signals that used to be split across paid tiers.
Includes
—Access to /api/v1/feed, /api/v1/cluster/:id, /api/v1/search, /api/v1/archive
Every absence is a product decision. If you need any of the above, Zaviye is politely not the right API.
Acceptable use — the short version
What you can do
Build commercial products on Zaviye data, including paid end-user products
Display cluster data, framing analysis, and bias breakdowns in your UI
Cache responses within the data window of your tier
Train models on response data, credited to Zaviye
Combine Zaviye data with other sources
What you can't
Resell raw article URLs as if they were a feed you own
Ship a product that looks like a Zaviye clone (brand imitation)
Use Zaviye data to generate disinformation, targeted harassment, or engagement-bait content
Share your API key with parties outside your organisation
Circumvent rate limits via multi-account registration
Full policy lives at /developers/aup (coming). Keys may be revoked for policy violations with 30-day notice except for acute misuse, where revocation is immediate.
Heavy or unusual use — tell us
Building something that needs more than the free tier covers?
There's no paid tier above this one — but if you're training a model on the corpus, need archive dumps, or have a usage pattern the free quota doesn't fit, tell us and we'll work it out directly. No sales call, no invoice.
