Context.dev - One API to scrape, enrich, and extract the internet
by•
Context.dev is the web context API for AI products and agents. Scrape any URL, crawl sites, turn pages into LLM-ready Markdown, extract structured data into your own schema, capture screenshots, and retrieve logos, colors, fonts, styleguides, company data, and transaction enrichment through one API. YC-backed, no card required, and built so developers or coding agents can integrate in minutes.
Replies
@yahia_bakour3 The product looks solid, but I’m interested in the competitive side. If someone already has Firecrawl or a similar API in production, what’s the biggest reason they decide to move to Context.dev? I’d love to know which feature or capability ends up being the deciding factor in real customer deployments rather than just in demos.
Context.dev
@josh_bennett1
Do you want your error rate to plummet?
Do you want best in class quality?
Do you want to cut your bill by 50-80%?
If the answer to any of these 3 is yes, then the answer is clear.
Id like to emphasize firecrawl is a wonderful company and i look forward to winning vs them and much larger competitors.
The agent-native onboarding is the part that stopped me, most APIs assume a human reads docs and wires a key in manually. Letting a coding agent paste one line, sign itself up, and grab a key end to end is a genuinely different distribution bet.
That's also my real question: what stops that flow from becoming a free-tier abuse vector? If an agent can self-provision with no human in the loop, nothing stops another agent from looping ten signups to dodge rate limits. Is there verification or a review gate before a self-signed-up key actually starts working?
Congrats on the launch!
Context.dev
@keirodev we have really advanced fraud protection. We get attacks nearly daily for the past year and have developed our own way of stopping it immediately and preventing it all-together
Really good question.
@yahia_bakour3 Good to know the system is battle-tested, a year of near-daily attacks is real signal ! Still curious whether it holds the same way for the agent-native path specifically, a human signup gives you a browser session, a device fingerprint, maybe a captcha to key off of, an agent hitting the API directly hands you far fewer signals to work with. Is that flow covered by the same system, or does it get extra friction (email verification, per-IP rate limiting) because it's a thinner surface to catch fraud on?
Context.dev
@keirodev yep, caught there too!
Plugged it into a side project and the brand extraction returned logos and fonts on the first try, which honestly surprised me for a 10 minute setup.
Context.dev
@beratzgll SUPERB!
How does the brand data extraction actually work under the hood when a site uses lazy loading or dynamically renders its content client-side?
Context.dev
@melisao2k9 we use a near perfect custom browser, so doesn't matter if they use lazy loading or not! you can try it out now :)
Didn’t know I’d love scraping websites, extracting style guides, and pulling font data until I tried context.dev.
There’s a surprising amount of knowledge to gain from doing things like this.
Context.dev
@chmielwork AMEN, there's so many possibilities!
How does it actually handle sites that load content dynamically with JavaScript, does it run a real browser under the hood or just hit the raw HTML and miss half the page?
Context.dev
@tahsincceuqp4 every single request goes through a browser. JS is always assumed to be there, we've found anything less affects quality dramatically.
Slashy
Have been a user for 9 months haven't had any problems.
Would recommend
Context.dev
@harsha_gaddipati you were actually my first ever YC-backed customer! It's crazy that we now live 2 doors down from each other man.
Thank you.
I can already think of a ton of use case for this. Congrats on the launch Yahia!!
Context.dev
@haita Amen, these fine people agree as well: https://www.context.dev/customers
The tricky part on that hash is that 'material' is consumer-specific: a price flip matters to a catalog agent, a nav reshuffle doesn't, but an agent watching layout wants the reverse. If you can surface the structured diff and let the caller pick which spans count, with your materiality hash as the sensible default, you sidestep everyone fighting one baked-in definition of meaningful. Glad it's already on the roadmap.
Context.dev
@dipankar_sarkar 100%, it's a really hard problem to solve developer-experience wise, we iterate more on the interface than the actual tech just because we want it to be intuitive for everyone.
What's your background btw? these are very solid questions.
🚀🌚
Context.dev
@maximehugodupre i agree