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.
Hey Product Hunt 👋
I’m Yahia, founder of Context.dev.
I built Context.dev because every AI product eventually runs into the same problem: models are powerful, but they don’t know what’s happening on the live web.
So teams end up building the same annoying infrastructure over and over again: scrapers, crawlers, browser rendering, proxy handling, sitemap parsing, Markdown cleanup, screenshots, logo extraction, brand enrichment, company data pipelines, and more.
Context.dev turns all of that into one API.
You can scrape any URL, crawl a site, extract clean LLM-ready Markdown, pull structured data into your own schema, capture screenshots, retrieve logos/colors/fonts/styleguides, enrich companies, and give your agents fresh web context in seconds.
The part I’m most excited about: Context.dev is agent-native. You can integrate it yourself, or paste one line into your coding agent and let it sign up, grab an API key, and wire the API into your codebase.
We’re YC-backed, have a free tier with no card required, and are already powering products at teams like Mintlify, daily.dev, DocsBot, Chatwoot, and more.
Would genuinely love feedback from the PH community, especially from anyone building AI agents, RAG pipelines, onboarding flows, enrichment workflows, or anything that needs live web data.
Happy to answer questions all day!
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.
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!
@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.
@yahia_bakour3 How do you measure extraction quality? Returning data is one thing, but making sure it’s accurate enough for production AI workflows is a much harder problem.
Awesome product Yahia! Glad I never have to handle scraping on my own again!
Putting crawl, Markdown cleanup, brand data, and schema extraction behind one API is a useful shape for agent builders! The place I would care about most is freshness, because stale web context can quietly poison a workflow. Do responses include enough source and timestamp detail for an app to decide when to reuse context and when to fetch again?
Typed SDKs across TS/Python/Ruby plus sub-10-min integration is a great combo. Curious how you handle caching/rate limits when a customer wants to enrich brand data for thousands of domains in one batch - queued async or synchronous per call?
A customer here , product is very dope and save us lot of money and time. If you are founder Yahia is kind of founder who go through every message and try to make himself available.
Right, I wasn't doubting the render fidelity, I meant determinism across fetches. Same URL scraped today vs next week: if the live DOM reorders a section, the markdown shape moves with it and an agent that indexed against the first shape drifts. Do you expose a content hash or a diff between fetches, so a pipeline can tell 'page actually changed' from 'page just reordered'? That's the bit that decides whether I wire it into an agent loop or keep it a one-off pull.
Treating web context as a first-class infrastructure concern rather than a DIY afterthought is exactly the kind of abstraction AI-native apps have been missing.
Interesting. Congrats on the launch. How does it handle sites with aggressive bot protection or frequent layout changes?
Nice work! The UI looks clean. I'm curious, what was the biggest challenge while building this?
Been using context.dev for a personal project since back when it was brand.dev. I'm not technical, I just build with AI, so being easy to use with an agent was my number one thing. Product aside, Yahia is just a really nice guy. Gave me some free credits, then topped me up again when I ran out. We're now a customer at the company level too, and I'll definitely be reaching for it on more projects going forward.
Amazing product, but more than that, amazing founder.
Context.dev solved an exact problem we had and we've actually shifted a lot of our architecture around their service because it's so good.
But beyond that, since I became a customer the founder Yahia has offered such amazing support that we have become friends. He's an intelligent, kind hearted guy and gives me a lot of advice on my business as we go through growth pains.
I highly recommend context and the ability to use something made by Yahia!
Big fan of Context.dev using it to personalize all our sales outreach!
We are using Context.dev and we love it! Recommended
Been a happy customer for a while and case study. Best and most affordable for brand extraction APIs for highly personalized experiences in my SaaS and marketing.
Expanding usage to full scraping soon!
About Context.dev on Product Hunt
“One API to scrape, enrich, and extract the internet”
Context.dev launched on Product Hunt on July 2nd, 2026 and earned 469 upvotes and 92 comments, earning #2 Product of the Day. 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.
Context.dev was featured in API (98.3k followers), Artificial Intelligence (472.5k followers) and Data (2.4k followers) on Product Hunt. Together, these topics include over 115.9k products, making this a competitive space to launch in.
Who hunted Context.dev?
Context.dev was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Context.dev stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Garry Tan