EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2025–2026

Context.dev bets AI agents need live web data; one API, 400+ customers

Solo founder's Brand.dev pivot lands YC S26: Launch HN 119 pts/86 comments, 400+ customers, one API for scraping and brand data.

Context.dev

The betAI agents and products shouldn't build crawlers; one API that returns clean markdown, structured extraction and brand intelligence will become the web context layer.Live

What the business is

Context.dev is a web-data API: developers send a URL, domain or sitemap and get clean markdown, HTML, screenshots or schema-shaped extraction, plus brand and company intelligence such as logos, colors and firmographics.

How it started

Solo founder Yahia Bakour (led engineering at Sunrun, worked at Amazon, previously co-founded StockAlarm.io and essense.io, both acquired) built Brand.dev and then Context.dev. YC rejected him once before accepting him into Summer 2026 as a solo founder.

What happened

Launched on Hacker News July 9, 2026 (119 points, 86 comments), positioning against Firecrawl with a '1 credit = 1 scrape' stance and no hidden credit multipliers. YC Launch on August 5, 2026 reported 400+ customers; the company is four people, serving Mintlify, Klarna, DocsBot, Super, Vizzy, Passionfroot and Rho, with plans from a free tier to Enterprise.

No ending yet — it is still running.

Background

Context.dev is a YC S26 startup by solo founder Yahia Bakour: one API that turns any website into structured data for AI agents — clean markdown, rendered HTML, screenshots, schema-shaped extraction, and brand intelligence such as logos, colors and firmographics. Bakour previously led engineering at Sunrun, worked at Amazon, and co-founded StockAlarm.io and essense.io, both acquired.

The product grew out of Brand.dev, a narrower API that returned logo and brand metadata to enrich onboarding. Customers kept asking for scraping, screenshots and structured extraction, so Bakour rebuilt it as Context.dev and applied to YC — rejected once, then accepted into Summer 2026 as a solo founder.

Context.dev launched on Hacker News on July 9, 2026 (119 points, 86 comments), positioning against Firecrawl with a simple pricing stance: one credit per scrape, no hidden multipliers, with residential proxies and JS rendering included. Its YC launch in August 2026 cited more than 400 customers, including Mintlify, Klarna, Passionfroot and Rho; the site claims 5K+ developers and a four-person team.

What has to be true

  • The wedge-to-platform path was customer-driven: every expansion — scraping, extraction, brand data — was something existing Brand.dev users explicitly asked for.
  • Agents genuinely need current web context, and most teams shouldn't maintain crawlers; a clean API fits the 'don't build data infrastructure' rule.
  • Self-serve distribution: free tier, one-line agent setup and transparent pricing made the Launch HN thread and 400+ customers possible without a sales team.

What can be applied

Listen to the wedge's customers: the asks that overflow a narrow API's scope (scraping, screenshots, extraction) are the roadmap to a bigger layer, not scope creep.

Aftermath

As of 2026-09-02, Context.dev is a live, four-person company in YC S26. Its YC launch (Aug 2026) reports 400+ customers — Mintlify, Klarna, Passionfroot, Rho, Super, Vizzy and DocsBot — and the website claims 5K+ developers on the platform. Pricing runs from a free tier (500 credits) to Developer $25/mo, Pro $149/mo and Scale $499/mo, with Enterprise for high volume. It continues expanding from scraping into brand intelligence, structured extraction, batches and monitors for agents.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases