q parameter — the topic in the URL path selects the feed:
Topics
topic is a path segment: GET /api/v1/news/:topic. 23 topics are available.
An unknown topic returns
404 with the full list of valid slugs — see unknown topics below.
Parameters
Response
The response uses the same shape as/api/v1/search: title, results, metrics, and (when available) images. A news array is always present.
results and news contain the same articles — only the order differs. Reach for results when you want the best headlines first, and news when you want a chronological feed.
Unknown topics
Requesting a topic that doesn’t exist returns404 with every valid slug, so a client can discover the full list from a single failed call:
Errors
401, 402, and 429 follow the same patterns as the search endpoint — see error handling.
Pricing
News requests are billed the same way as a search request: a per-token rate on the returned content, with no flat per-call fee. The charge is returned inmetrics.cost_dollars, the same field the search and fetch endpoints use.
Cache hits are billed the token rate only (no vendor call runs), and are marked
cached: true in metrics, alongside cache_age_seconds — see metrics.
Use cases
The news endpoint is built for fixed, recurring feed requests — the kind of thing a slash command or a scheduled agent job asks for repeatedly, like “latest world news” or “programming news.” Because the topic is fixed, there’s no query to construct and no need for a separate fetch pass to pull in full articles: one call returns a ranked, deduplicated, freshly-dated feed ready to hand to a user or an LLM.Next steps
Response format
Full response structure and result fields.
Content retrieval
Fetch the full text of any article returned in a feed.
News monitoring example
Build a query-driven news monitor with the search endpoint.
Error handling
Status codes and retry strategies.

