{"slug": "context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai", "title": "Context.dev bundles scraping, brand data and screenshots into one API for AI agents", "summary": "Y Combinator-backed Context.dev launched a unified API that bundles web scraping, brand data extraction, and screenshot capture for AI agents, replacing the need for developers to build custom data pipelines. Founded by solo founder Yahia Bakour, the product turns URLs into structured outputs and already powers tools at companies including Super.com, Klarna, and Similarweb. The July 2nd Product Hunt launch ranked #1 product of the day, reflecting demand for live web context as a default primitive in AI products.", "body_md": "[Yahia Bakour (@mynameisyahia)](https://x.com/mynameisyahia?ref=runtimewire) is taking [Context.dev](https://www.context.dev/?ref=runtimewire) public as a [Y Combinator Summer 2026](https://www.ycombinator.com/companies/contextdev?ref=runtimewire) company with a simple pitch to agent builders: stop rebuilding the same web-data plumbing every time a product needs fresh context.\n\nThe product turns a URL or domain into structured outputs through a single API. Context.dev says developers can use it to scrape pages into clean Markdown or rendered HTML, crawl sitemaps, extract fields into a user-defined JSON schema, capture screenshots, pull logos, colors, fonts and styleguides, retrieve company metadata and enrich transaction strings into recognizable brands. Its homepage says the API is already powering products and agents at Super.com, Passionfroot, Mintlify, Chatwoot, Similarweb, Klarna, DocsBot, Daily.dev, Vizzy, Comp AI and ION.\n\nThe timing matters. Context.dev was founded in 2025, according to [Y Combinator's company profile](https://www.ycombinator.com/companies/contextdev?ref=runtimewire), and Bakour announced on May 31st that Context.dev was backed by YC. The company had already rebranded from Brand.dev to Context.dev on March 21st, according to its [docs changelog](https://docs.context.dev/changelog?ref=runtimewire), a naming shift that tracks the product's expansion from brand enrichment into a broader web extraction layer. Its [Product Hunt launch](https://www.producthunt.com/products/context-dev?launch=context-dev&ref=runtimewire) on July 2nd ranked #1 product of the day, giving the solo founder a distribution moment one week before the July 9th public posting.\n\n### A founder selling pain he already lived\n\nBakour is not coming at scraping as a first-time infrastructure tourist. YC lists him as Context.dev's active founder and says he previously worked as a principal software engineer and manager at Sunrun, an Amazon SDE II and tech lead on a tier-1 retail checkout platform, and co-founder of Stock Alarm, a bootstrapped stock and crypto alerts app that reached 225,000-plus users and 100,000-plus daily notifications before it was acquired.\n\nHis own site adds a founder-heavy resume: [Essense.io](https://yahiabakour.com/?ref=runtimewire), which he says was acquired by Optic, a staff engineering stint at Optic, and earlier roles at Bank of America Merrill Lynch and Libring. The relevant throughline is repeated data infrastructure. Bakour wrote on Product Hunt that he built Context.dev because every AI product eventually has the same problem: the model can reason, but the product still needs to know what is happening on the live web. Teams then rebuild scrapers, crawlers, browser rendering, proxy handling, sitemap parsing, Markdown cleanup, screenshots and brand enrichment.\n\nThat is the wedge. Context.dev is selling convenience, but the deeper product bet is that live web context becomes a default primitive inside AI products, the way payments, auth and search became outsourced primitives for earlier generations of software. Bakour is pricing Context.dev like an infrastructure component developers can test quickly, then leave in production if the data quality holds.\n\n### What Context.dev actually bundles\n\nContext.dev's [documentation](https://docs.context.dev/introduction?ref=runtimewire) describes structured JSON responses. The output menu includes company profiles, social handles, NAICS and SIC codes, website styleguides, fonts, Markdown and HTML, screenshots, brand assets, and product data. The API is aimed at workflows where an agent or app needs current external data in a shape it can use without a custom parser.\n\nThat bundle puts Context.dev across several markets at once. One part competes with scraping and crawling APIs. Another part competes with logo and brand-data providers. Another part touches company enrichment and transaction cleanup. Context.dev's own [comparison page](https://www.context.dev/compare?ref=runtimewire) names alternatives including Firecrawl, ScraperAPI, ScrapingBee, Spider, Browse.ai, Jina AI, Apify, Crawl4AI, Tavily and Exa on the scraping and search side, and Brandfetch, Logo.dev, Clearbit Logo, Parqet, RiteKit and Klazify on the brand side.\n\nThe practical difference Bakour is pushing is packaging. A product team building an onboarding flow might want to infer a customer's company from a work email, pull the logo and colors, generate a branded setup screen, crawl the customer's docs, and feed clean pages to an agent. Context.dev wants all of those calls to happen under one API key rather than across a scraper, a logo service, an enrichment provider and a screenshot tool.\n\nThe company's customer page reads like a map of that strategy. [Mintlify](https://www.context.dev/blog/mintlify-turns-github-repos-into-branded-docs-sites-with-brand-dev?ref=runtimewire) used Context.dev to help turn a GitHub repo URL into a branded docs site. [Similarweb](https://www.context.dev/blog/similarweb-10x-ai-agents-with-context-dev?ref=runtimewire) uses Context.dev across scrape and brand APIs for internal AI workflows. Context.dev says SiteGPT moved from Firecrawl to Context.dev for website scraping behind customer-support bots, while DocsBot uses it to reduce onboarding friction. These are company-published case studies, so they establish Context.dev's own customer narrative rather than independent performance benchmarks.\n\n### The business model is usage-first\n\nContext.dev's [pricing page](https://www.context.dev/pricing?ref=runtimewire) starts with a free tier and 500 API credits for work-email signups. Paid plans run $25 per month for Developer, $149 per month for Pro and $499 per month for Scale, with Enterprise above 2 million monthly credits. The company prices simple scraping calls at 1 credit per page and says JS rendering, anti-bot bypass and premium proxies are included without separate surcharges. More advanced calls, including brand retrieval, styleguide generation and structured extraction, cost 10 credits.\n\nThat pricing makes the fight concrete. Context.dev is trying to make the first integration cheap enough for a developer or coding agent to add during product buildout, then capture volume as the feature moves into production. The homepage even includes an agent setup path that tells users to paste one line into a coding agent so it can sign up, fetch an API key and wire Context.dev into the codebase.\n\nThe funding story is still sparse. Context.dev is backed by [Y Combinator](https://www.ycombinator.com/companies/contextdev?ref=runtimewire), and YC names Jon Xu as the company's primary partner. No priced round, valuation or non-YC investor has been disclosed. YC's [published standard deal](https://www.ycombinator.com/deal/?ref=runtimewire) is $500,000, with $125,000 converting into 7% and $375,000 on an uncapped MFN safe. That describes YC's standard terms, not a company-specific valuation for Context.dev.\n\n### What remains unproven\n\nThe sharp question for Context.dev is data quality under messy production traffic. Scraping and enrichment APIs are easy to demo against clean pages. They become harder when sites change layouts, bot defenses tighten, content is cached too long, logos are wrong, or an agent quietly acts on stale context.\n\nThe company's own claims about customer count also vary by source. YC says Context.dev powers agentic products at Mintlify, Super, Vizzy, Klarna and 280 other companies. Product Hunt says it is trusted by 5,000-plus businesses. Context.dev's homepage shows recognizable customer logos and says 5,000-plus developers in a testimonials section. Those are self-reported adoption signals with different denominators.\n\nStill, Bakour has chosen a real problem at the right layer. Agent builders keep discovering that model capability is limited by the freshness and shape of the data they feed it. Context.dev's opportunity is to turn that repetitive integration work into a default API call. Its risk is that the same breadth that makes the pitch attractive also raises the bar: customers will expect scraping, brand identity, company enrichment, screenshots and transaction cleanup to behave like one dependable system, even though each category has its own failure modes.", "url": "https://wpnews.pro/news/context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai", "canonical_source": "https://runtimewire.com/article/context-dev-yahia-bakour-yc-s26-web-data-api", "published_at": "2026-07-09 16:39:04+00:00", "updated_at": "2026-07-09 16:51:38.626742+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-infrastructure", "developer-tools", "ai-products"], "entities": ["Context.dev", "Y Combinator", "Yahia Bakour", "Super.com", "Klarna", "Similarweb", "Product Hunt", "Brand.dev"], "alternates": {"html": "https://wpnews.pro/news/context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai", "markdown": "https://wpnews.pro/news/context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai.md", "text": "https://wpnews.pro/news/context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai.txt", "jsonld": "https://wpnews.pro/news/context-dev-bundles-scraping-brand-data-and-screenshots-into-one-api-for-ai.jsonld"}}