Context.dev (YC S26)

🔓 case study unlocked: marketbetter (mb)ᵃⁱ MarketBetter uses Context.dev (YC S26) to give SDRs everything they need before a call; company intel, what got the reply, and an on-brand deck with the prospect’s latest logos, colors, and imagery. "All of this intel comes in from Context.dev (YC S26), and we marry it with CRM data: what we emailed them, what actually got the reply, and what actually led to the meeting. The SDRs have the full context, so they know exactly what to say." - Sunder S.o say." - Sunder S. Case study below!

PSA: new case study unlocked 🔓 Adapt helps insurance agencies automate the manual work of retrieving, processing, and routing documents from carrier portals. Behind the scenes, their GTM team is applying that same automation mindset at serious scale: 20K+ CRM accounts, ~6,000 monitored websites, AI agents acting on real web signals. In our latest case study, we break down how Adapt uses Context.dev (YC S26) to: > Add recognizable logos across 20K+ accounts without maintaining an asset library > Monitor thousands of account and industry websites for meaningful changes > Surface signals like new offices and leadership changes to the right AE > Ground GTM agents in real website evidence before signals hit HubSpot or Slack > Get up and running through MCP in minutes The result: no scraping infrastructure to build or maintain, less manual website checking, and fewer opportunities lost to bad or missing web data.

🔓 Case study unlocked: Gene Inspector Pro Gene Inspector Pro built Diana, an AI agent that helps users investigate health questions using their DNA data and current genetics research. To make that work, Diana needs reliable access to up-to-date scientific literature, without Gene Inspector Pro having to build and maintain a separate web-access stack. That’s where Context.dev (YC S26) comes in. Context powers both: > Gene Inspector Pro’s broader literature discovery pipeline > Diana’s user-driven research into genes, variants, and supporting evidence while importantly: users’ genomic data never gets sent to Context.dev. Read how Gene Inspector Pro is using Context.dev to keep Diana grounded in current research ↓

PSA: case study unlocked 🔓 Knowlify (YC S25) turns documents, blog posts, and ideas into narrated, animated videos. But there was one problem: getting accurate web data + brand assets into those videos consistently. They had been using Brandfetch & others, but ran into limited features, inaccurate results, and a lack of support. So they switched to Context.dev (YC S26) The migration took less than 5 minutes. Using our premade prompts for coding agents, Knowlify was able to get the integration built, tested, and shipped almost immediately. > More accurate client brand assets > Happier customers > Less manual asset work > Broader brand data from one platform As Knowlify co-founder Arjun put it: “For all features of their product, you're able to get it set up using their premade prompts for agents. It took less than five minutes to get everything built and shipped.” And they’re already planning to bring Context.dev (YC S26) into their onboarding workflows next.

Now that launch week is over, back to regularly scheduled programming PSA: Case study unlocked AI agents don’t just need better models. They need better context. Spikonado is building Sprocket, an AI engineering agent that works across hardware, frameworks, tools, and dependencies. The problem: all of those things change constantly. So instead of relying only on what the underlying model already knows, they gave Sprocket a way to pull fresh documentation at runtime using Context.dev (YC S26) The integration took about an hour. And according to founder Aarav Gupta, it made the agent “massively more reliable.” That’s the part I find interesting. The agent itself didn’t need to change. The improvement came from giving it a reliable path to the right source material at the exact moment it needed it.

New customer case study 🔓 Layers originally came to Context.dev (YC S26) for a simple feature: automatically showing customer logos inside its dashboard. But while integrating our Logo API, founder Jake Casto discovered our URL-to-Markdown API, and realized it could replace a Cloudflare setup that had been causing reliability issues. He gave our docs to Devin AI, and in under 30 minutes, Layers had shipped both: > Automatic customer logos > A more reliable Markdown pipeline > Two production integrations completed in one session What started as a small visual improvement turned into an infrastructure upgrade. That’s the kind of developer experience we’re building at Context.dev: clear docs, agent-friendly APIs, and useful integrations that ship fast. Link below

PSA: case study unlocked 🔓 Amorphic Labs (YC S26) creates personalized demo videos for every stage of the customer journey. The product starts with a list of prospects, then personalizes each video using information about the company watching it. One small but important part of that experience: making every prospect instantly recognizable. Amorphic Labs uses Context.dev (YC S26) to automatically turn company names into the correct logos and enrich its prospect list before each video is generated. Dylan Kelly, CEO of Amorphic Labs, integrated the API with coding agents in just a few minutes: “The API integration was super easy to set up. We didn't run into any problems, and it only took a few minutes with agents to get set up.” Now, every prospect can receive a branded demo without the Amorphic team manually searching for, downloading, and managing company assets. Company name in. Personalized demo out. Full case study below 👇

PSA: case study unlocked 🔓 Takkie AI lets businesses launch customer support agents trained directly on their websites. They originally used Cloudflare's Markdown API because it was free, but it kept failing and training runs wouldn’t finish. Then founder Bazzo Kelesh found Context.dev (YC S26) “In under 30 minutes I migrated our code from Cloudflare Markdown to Context.dev in production.” Now Takkie users can train agents on: > a single page > a filtered website crawl > an entire sitemap A scraping infrastructure migration, shipped to production in one sitting.