Context.dev, the company that grew out of Brand.dev, raised a $9M seed led by General Catalyst, and a thread on r/AI_Agents is arguing over what web access for agents will still be worth in a year.
Another week, another round for web data for agents. This time it's Context.dev, which sells one API to search, scrape, crawl and monitor the web, for products and for agents. Its founder, Yahia Bakour, announced the round on the company blog, in a post dated October 19, 2026 in search results. General Catalyst led. The Reddit post and an Instagram post we found in search also name Orange Collective and Robinhood Ventures as investors, but the blog post itself doesn't list them.
Honestly the funding isn't the interesting part. The thread on r/AI_Agents has 18 points and 14 comments, and most of them skip the money and argue about the business.
What's actually new
The money is new. The product isn't, and the blog post is pretty open about where it came from.
The company started as Brand.dev, pulling logos, colors and fonts from websites so an app could greet a new customer with their own brand instead of a blank form. Then customers asked for more. Could it pull products from a site? Answer a question about a company? Turn a page into clean Markdown, crawl a whole domain? The founder says he usually said yes.
Then agents showed up and the question changed, in his words, to "how does my agent read the internet?" Earlier this year Brand.dev became Context.dev.
The post lists what customers use it for today. Keeping data fresh on more than 20 million companies. Powering 3,000+ integrations. Giving Similarweb's AI agents the datapoints they need. Building a 2M+ food and supplement database. Shipping an onboarding MVP in an hour. These are the company's own claims btw, and the post doesn't link to case studies.
Two more details matter if you're a developer. The company says it launched a feature called Highlights, "so agents spend their tokens on the parts of a page that matter." And it says it has never shipped a breaking change. Pricing is self-serve, with 1,000 free credits a month and no card needed. Search snippets for the company's LinkedIn and Dealroom coverage describe it as part of Y Combinator's Summer 2026 batch, and the blog thanks Y Combinator.
Why it matters if you build agents
The original Reddit post framed this as investors treating web access for agents as its own infrastructure category. It pointed to recent, bigger rounds at Exa and Firecrawl as proof. The figures in the post look garbled though (a "$25 Series C" for Exa, which one commenter read as $250m), and we couldn't confirm either one from our sources.
The more useful bit for builders is in the comments. As one person put it, anyone can curl a URL. What breaks agents is everything around the fetch. Sites block agents. Pages load half their content through JavaScript. Layouts change and extraction breaks without telling anyone. And worst of all, a block page can come back looking like real content, and the agent reasons over it like it's real.
Here's what that looks like in practice. Say your agent checks five competitors' pricing pages every morning and posts changes to Slack. One day a site puts up a bot check. If your provider hands that page back as plain text, your agent might cheerfully report "they removed all their plans" and you'd have no idea anything went wrong.
So when you pick a web data provider, judge it less on the happy path and more on how it fails. Does it tell you a page changed? Does it flag a captcha or block page, or just pass it to your agent as text? How does it deal with JavaScript-heavy sites? Those answers decide whether your agent gives you a wrong answer with full confidence.
And with the market this unsettled, keep the provider swappable. Don't wire one vendor's response format deep into your agent's logic. FWIW this is a spot where a gateway helps. MewCP has servers for Context.dev, Exa and Firecrawl in its catalog, so an agent can reach whichever ones you connect through one MCP address, and changing which tools an agent gets happens in the dashboard while the agent's code stays the same. Every call also lands in a log with which tool ran, when, whether it worked, how long it took and why it failed. MewCP never stores what the app sent back, so it won't catch a captcha page dressed up as content. But it shows which calls errored and when, which is usually where debugging starts.
What people are saying
Commenters on r/AI_Agents mostly agreed that raw fetching won't stay valuable for long. One argued frameworks will bundle basic scraping within a year, and what's left to charge for is failure handling, like "noticing you got a captcha wall served back as content." Another said the real edge is how fast a provider can rebuild extraction when a site changes its structure, and said they'd seen exactly that break three different agents in one week.
The sharpest pushback was that every company in this space is "one openai feature release away from a bad quarter." A reply disagreed, its argument was that these companies sell the operational pain of doing retrieval reliably at volume, and a model release doesn't make that go away. Another commenter said the lasting moat is data, meaning a durable index and real licensing deals. Someone replied that licensing is also a cost base a seed-stage company can't easily afford, so smaller players might have to win on something else or get bought.
On timing, one commenter compared it to proxy providers, a feature race that ends with everyone offering everything. Another figured consolidation would take three or four years, not eighteen months, with around six viable players in the meantime.
