CNET scraper API: articles as JSON
Send any CNET page URL with recipe=cnet and get title, description, url as JSON. No selectors to write, no proxies to pick.
- 1 page type
- 3 fields
- 5 credits a page · $0.50 per 1,000
- Working · 100% in 7 days
5,000 free credits for 7 days, no card.
curl -G 'https://api.ujeebu.com/scrape' \
-H "ApiKey: $UJEEBU_API_KEY" \
--data-urlencode 'url=https://www.cnet.com/tech/services-and-software/vpn/' \
--data-urlencode 'recipe=cnet'
{
"result": {
"title": "VPN",
"description": "Learn about VPN on CNET"
},
"success": true
}
What you get from CNET
The fields of each page type and a real sample from our last validation, shortened.
Articles recipe=cnet 5 credits a page
| Field | Type | Example |
|---|---|---|
title | text | VPN |
description | text | Learn about VPN on CNET |
url | URL | https://www.cnet.com/tech/services-and-software/vpn/ |
Sample answer, validated 2026-11-04
{
"title": "VPN",
"description": "Learn about VPN on CNET",
"url": "https://www.cnet.com/tech/services-and-software/vpn/"
}
One call
Send the page URL and the recipe name to the Scrape API. The recipe brings the extract rules and the settings that work on CNET (JavaScript rendering).
curl -G 'https://api.ujeebu.com/scrape' \
-H "ApiKey: $UJEEBU_API_KEY" \
--data-urlencode 'url=https://www.cnet.com/tech/services-and-software/vpn/' \
--data-urlencode 'recipe=cnet'
import os, requests
r = requests.get(
"https://api.ujeebu.com/scrape",
params={"url": "https://www.cnet.com/tech/services-and-software/vpn/", "recipe": "cnet"},
headers={"ApiKey": os.environ["UJEEBU_API_KEY"]},
timeout=120,
)
print(r.json()["result"])
const params = new URLSearchParams({
url: "https://www.cnet.com/tech/services-and-software/vpn/",
recipe: "cnet",
});
const res = await fetch(`https://api.ujeebu.com/scrape?${params}`, {
headers: { ApiKey: process.env.UJEEBU_API_KEY },
});
console.log((await res.json()).result);
The answer is {"result": {...}} with the headers Ujb-Recipe and Ujb-Credits. Your own parameters always win over the recipe.
What people build with CNET data
Media monitoring
Track the articles published on the topics and companies you follow.
Learn moreContent for AI and RAG
Collect headlines, dates and summaries as structured input for search and LLM pipelines.
Learn more
Price
Same price as the page call, no fee for the recipe. Only successful responses are billed; blocked, timed-out and failed requests are free.
| Page type | Credits a page | Per 1,000, Starter | Per 1,000, Pro |
|---|---|---|---|
| Article | 5 | $0.82 | $0.50 |
FAQ
What does the CNET recipe return?
JSON with 3 fields from article (recipe=cnet), for example title, description, url. The answer is {"result": {...}} with the fields shown on this page.
How much does it cost to scrape CNET?
5 credits a page ($0.50 per 1,000 on Pro, $0.82 on Starter). Same price as the page call, no fee for the recipe. Only successful responses are billed; blocked, timed-out and failed requests are free.
Do I need proxies or a headless browser?
No. The recipe brings the settings that work on CNET: JavaScript rendering. Send only the URL and recipe=cnet.
What happens when CNET changes its pages?
We check CNET every day and re-validate the recipe on real pages every week, then fix it when the site changes. Until a fix is live, the API answers 404 "the recipe has no working version" instead of empty data, and that call is free.
Can I change the fields?
Yes. Send your own extract_rules or any setting (js, proxy_type, wait_for) and it wins over the recipe. The developer guide shows the recipe rules to start from.
Related recipes
- SubstackArticle · 5 credits
Yahoo FinancePage · 5 credits
Yahoo NewsSearch results, Article · 5 credits
AFP Fact CheckArticle · 5 credits
Al JazeeraArticle · 5 credits
Ars TechnicaSearch results, Article · 5 credits
Logos and names belong to their owners. Ujeebu is not affiliated with CNET.
Get CNET data as JSON today.
5,000 free credits for 7 days. No card.