Search the news for a topic
Run job:news.search through the looot API: 6 providers, from $0.00099 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Search the news for a topic.
Job id news.search, in Web search & research (Web data). As of 2026-10-01, 6 providers serve it through 7 tools. Run job:news.search and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
A job run takes shared input names; looot maps them to each provider’s own fields. See Job inputs.
| Input | Taken by |
|---|---|
language |
6 of 6 providers |
query |
6 of 6 providers |
country |
4 of 6 providers |
limit |
4 of 6 providers |
domain |
3 of 6 providers |
device |
2 of 6 providers |
location |
2 of 6 providers |
url |
2 of 6 providers |
Any other key you send passes through unchanged. Each tool’s own fields are on its page below.
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| AnyAPI | anyapi-run-google-news |
$0.00099 per call |
| DataForSEO | dataforseo-google-news-advanced |
$0.002 per call |
| DataForSEO | dataforseo-google-news-html |
$0.002 per call |
| Cloro | cloro-monitor-google-news |
$0.004 per call |
| Brave Search | brave-search-res-news-search |
$0.005 per call |
| NewsData.io API | newsdata-io-1-latest |
$0.01 per call |
| Anysite | anysite-api-google-news-articles-search |
$0.036 per call |
A call that fails at the provider costs $0. See What’s free.
Output
Each provider answers in its own shape. Shape of the run’s result from newsdata-io-1-latest, checked against 2 real answers:
{ status, results: { link, title, ai_org, ai_tag, content, country: string[], creator: string[], pubDate, category: string[], datatype, keywords: string[], language, ai_region, duplicate, image_url, pubDateTZ, sentiment, source_id, video_url, ai_summary, article_id, fetched_at, source_url, description, source_icon, source_name, sentiment_stats, source_priority }[], nextPage, totalResults }
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:news.search","input":{"domain":"example.com"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:news.search",
input: {
domain: "example.com",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:news.search",
"input": {
"domain": "example.com",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:news.search.