Context.dev
Web data API in Developer tools
Developers recommend it as a structured-data API for websites that saves them from running their own scraping infrastructure, with transparent per-scrape credit pricing.
Developers recommend it as a structured-data API for websites that saves them from running their own scraping infrastructure, with transparent per-scrape credit pricing.
15 people gave an opinion
- recommend it
- 11
- criticize it
- 4
- approval share
- 73%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 11 people recommend itNeeds 10 or more, met.
- 2.8 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Transparent pricing with no hidden multipliers
“i'm an engineer by trade, and always hated things like forcing a sales call, or having hidden credit multipliers”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “we're cheaper than every other option out there, because there's no hidden credit multipliers”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “1 credit = 1 scrape, no hidden credit multiplier”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” One credit per scrape, all included
“it's all included in the credit price, great value compared to alternatives”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “we're cheaper than every other option out there, because there's no hidden credit multipliers”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” Removes need for in-house scraping
“one of those rare APIs that immediately made a problem I had disappear”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “teams migrate to us from in-house solutions all the time”
Comment from 10 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “the infra needed to support something like a few hundred TPS w a browser fleet would cost more than a sub to us”
Comment from 10 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” Responsive support and improving product
“Yahia was very helpful in providing support and discount!”
Comment from 10 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “Been great watching this product improve so quickly”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website”
What people warn about
Each mark is one comment
Scraping conflicts with robots.txt
“robots.txt already exists and is commonplace but if we actually followed it our solution wouldn't work”
Comment from 10 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website” “Great, another thing I have to block server side.”
Comment from 9 Jul 2026 in “Launch HN: Context.dev (YC S26) – API to get structured data from any website”
What people said
20 of the 22 comments that mention it, newest first. Each links to the original comment.
“Yahia was very helpful in providing support and discount!”
“teams migrate to us from in-house solutions all the time”
“Your docs don't respect system-mode choice until you click into light/dark mode then back to system.”
“Now I don't see the need for this.”
“robots.txt already exists and is commonplace but if we actually followed it our solution wouldn't work”
“This seems like a responsibly designed service, but I find it a little odd and baffling that we need such intermediaries”
“the infra needed to support something like a few hundred TPS w a browser fleet would cost more than a sub to us”
“get you 70% of the way to this well funded startup”
“lessgooo! context dev ftw!”
“it's all included in the credit price, great value compared to alternatives”
“i'm an engineer by trade, and always hated things like forcing a sales call, or having hidden credit multipliers”
“I like the clarity, tone, and readability of your webpage”
“we're more fully featured than cloudflare”
“Been great watching this product improve so quickly”
“going into production it makes sense to use a provider (like us)”
“one of those rare APIs that immediately made a problem I had disappear”
“we're cheaper than every other option out there, because there's no hidden credit multipliers”
“1 credit = 1 scrape, no hidden credit multiplier”
“Seems wildly expensive, furthermore not a single mention of "ip" on homepage?”
“Great, another thing I have to block server side.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.