Hyperspell builds the company brain for AI agents. It pulls together context from tools like Slack, email, Drive, and Notion, then synthesizes it into a shared source of truth that both people and agents can rely on.
For cofounder and CEO Conor Brennan-Burke, public web data belongs in that picture too. But getting it into Hyperspell had meant maintaining a waterfall across multiple crawling providers. Context.dev gave the team a simpler way to bring website content and structured company data into the brain.
A crawler waterfall the team had to babysit
Hyperspell was already pulling in a lot of public web data when Conor came across Context.dev. The team had assembled a fallback setup because no single crawling provider was dependable enough on its own.
"We had been doing a waterfall across multiple web crawlers because none of them was reliable enough on its own."
The setup worked, but each scraper brought its own edge cases. Keeping those providers working together meant maintaining infrastructure that Conor did not want his team spending time on.
"It worked, but this is exactly the kind of infrastructure I do not want my team spending time babysitting"
More than raw page content
Hyperspell needs public information that helps it build an accurate picture of a company. Website content is one input; brand information, company data, style guides, and documentation can all contribute useful context as well.
That made the breadth of Context.dev's API relevant to the product. Hyperspell could get different kinds of public data from one place as its needs grew.
"Context.dev was interesting because we could get a lot of that from one place rather than adding another vendor every time we wanted a new type of data"
The goal was to bring that public context together with the knowledge already in a company's internal tools, so people and agents could work from a shared source of truth.
An API the team could drop in
Conor first discovered Context.dev through YC and kept seeing founder Yahia Bakour online. When they spoke, the focus on reliability stood out. It was the team's biggest concern with its existing setup.
Getting started was straightforward:
"Context.dev was stupidly easy to drop in and replace that whole setup. The API makes sense, the docs are actually useful, and we got it working fast."
The integration let Hyperspell send more of its web data through one provider, reducing the need to build around each scraper's quirks. Conor also valued how quickly the Context.dev team moved.
"Yahia and the team also move absurdly fast, which I appreciate a lot"
Public web data inside the company brain
Context.dev now supplies website content and structured company data through one API. Hyperspell synthesizes those inputs alongside Slack, email, Drive, and Notion into the same shared source of truth.
As Conor puts it:
"Context.dev lets us treat the public web as a first-class input into the company brain. We can pull website content and structured company data through one API, then synthesize it alongside internal sources like Slack, email, Drive, and Notion into a shared source of truth. It’s made that whole part of the stack much simpler"
For Hyperspell, the result is a simpler web data stack supporting the work its product is built to do: give people and AI agents context they can rely on.
Building agents that need public web context? Explore Context.dev's web tools for AI agents.