Launch HN: Context.dev (YC S26) – API to get structured data from any website

context.dev

72 points by TheYahiaBakour 10 hours ago


Hi Hacker News, I’m Yahia. I built Context.dev (https://www.context.dev/) to make it really easy to integrate web data into your products and agents.

Here’s a demo video: https://www.tella.tv/video/build-faster-with-context-dev-api...

Since it’s an API, here are the docs: https://docs.context.dev/quickstart.

You can send us a URL and get back clean Markdown, rendered HTML, screenshots, extracted images, etc.. You can also send us a domain and get company or brand context: name, description, logos, colors, fonts, social links, screenshots, style information, and related metadata. For more custom use cases, you can send a URL plus a JSON Schema and ask us to extract structured data from the site into that shape. For example, you might ask for pricing plans, product categories, office locations, support links, integration partners, or anything else that is visible on the public site.

The goal is to give developers the output they actually want. Raw HTML is rarely the useful thing; the useful thing is usually Markdown for a model, JSON for an application, a logo for a UI, or a structured company profile for an agent.

Before, I worked at Amazon and Sunrun, and co-founded StockAlarm.io & essense.io, both of which were acquired. Also, I built knifegeek.io, which scraped pocket knives from across the internet and listed them easily. The project is outdated now (coming back soon) but back then it hit the frontpage of hacker news and people seemed to like it: https://news.ycombinator.com/item?id=34604281.

Just before Context.dev, I built Brand.dev. The idea was that your software product should automatically know about your customer if they sign up with a corporate email. The API pulled brand data such as logos, backdrops, name, description, industry, and more from the public web and surfaced it to your product to integrate as part of their onboarding experience. That’s worth doing because conversion rates on onboarding improve dramatically when you go from “enter all this info” to “confirm all this info” (and there was never any privacy concern all the information is public).

That was a nifty niche, but the more customers used it, it became obvious that “brand data” was only one slice of a larger need. People started asking for things like screenshots, structured extraction, and LLM ready data. So I expanded to Context.dev, and applied to YC (got rejected after an interview), then kept going and re-applied at which point I got in as a solo founder.

People use Context.dev in more ways than I can list, but here are some: keeping context up to date on customer websites for chatbots - building beautiful brand assets/ads for customers - enrichment flows using agent harnesses like eve.dev - crawling customer websites into chatbot knowledge bases - turning GitHub repos into branded docs sites - academic journal and PDF crawling. There are a ton more examples at https://www.context.dev/customers.

We know that many crawlers are not behaving like good citizens on the web, and the entire space has a bad reputation as a result. At the same time, customers are not usually trying to buy “scraping”. They are trying to make a support bot work, personalize onboarding, enrich CRM records, generate docs, monitor leads, or let an agent research a company. There are lots of legit use cases. We want to satisfy those while being respectful of everyone involved.

We maintain a caching layer and avoid hammering websites. Customers can configure the cache, but if we find we’re sending too many requests to a url in a certain amount of time, we step in and tone it down. Websites can opt out of our service, and we respect these requests and add them to our block list.

We focus on customers who want to build cool things for their users. Enriching onboarding is a popular use case. So is integrating context about their own websites (things like support bots), and building agents that can automatically reason about complex tasks involving the internet.

We only allow customers to use brand data to identify a specific customer on their software, you cannot use it in your own materials or to imply endorsement.

I'd love to hear your feedback about the product in the comments, thanks!

setgree - 8 hours ago

I like the clarity, tone, and readability of your webpage. Also your FAQ is refreshing

> When Should I talk to sales? > Talk to sales if you need high-volume pricing beyond 2M credits/month, custom rate limits, SSO / SAML, SCIM provisioning, an uptime SLA, annual invoicing, an MSA / DPA, or a dedicated support channel. Reach us at hello@context.dev or through the contact page.

Would that this were the norm everywhere, rather than (say) a sales rep from Datadog scraping my phone number from who knows where to ask about my company's needs after I sign up for a free account on a whim :)

twosdai - 8 hours ago

Are you using residential proxies? How do you handle websites that don't want to be scraped.

EG if I start passing in Linkedin pages what is your expectation of the result that people would see per profile.

EDIT:

Congrats on the launch seriously hard work, just wanting to understand your scraping stance more. I've worked with a lot of tools on this, didn't mean for my initial comment to be adversarial.

dataviz1000 - 6 hours ago

Have a look at Intercept. [0] I don't have a need for it, likely it is dated and will require some more tuning, and I want to get away from scraping. Creating typed Typescript proxy API for any website might be something you find useful.

> Reverse-engineers any website by doing a breadth search across every transport (JSON, WebSocket, WebRTC, GraphQL, SSE, HLS, PubSub), listing them all, and generating a typed JSON API that bypasses almost all bot protections — including Turnstile. I didn't include the ability, but it bypassed the most advanced ChatGPT + Turnstile. Built with self-improving Claude Code agents that rewrite their own instructions until fresh agents consistently succeed.

> Once connected to a page, it intercepts every byte of network traffic — then actively drives the page to surface endpoints that only fire on interaction. It types into forms, clicks buttons, scrolls, triggers modals, paginates, submits searches, and walks through multi-step flows, watching what each action produces on the wire. Every request gets captured with its method, headers, payload shape, and response, then classified by transport (JSON, WebSocket, WebRTC, GraphQL, SSE, HLS, PubSub). The result is a complete map of the site's real API surface — including the hidden endpoints that only exist behind a click — turned into typed proxy routes you can curl.

[0] https://github.com/adam-s/intercept

modo_ - 9 hours ago

I was using Context back when it was still Brand.dev. I found it to be a great product- one of those rare APIs that immediately made a problem I had disappear. Had it in production within an hour of signing up

Agents need clean/current context from the web, and this is the best way I’ve found to give it to them. The internet is clearly moving in this direction: companies are starting to realize their sites need to be legible to agents. Some are already adapting but many haven’t yet. Context feels like an important part of that transition

Yahia is a great builder. His pace of expansion has been impressive, excited to see where he takes Context.

m_w_ - 9 hours ago

Unclear what difference exists against Firecrawl - their team has been shipping great features extremely quickly lately, and their core offerings have become really good.

I am interested in KnifeGeek though - looking for a good OTF (ultratech?)

tomerlir - 4 hours ago

Really cool idea! I had something similar a while back. Maybe figure out a way to use MCP so the client can connect directly out of the box

korrectional - 7 hours ago

Hey Yahia, I recently saw your startup on the YC registry and found it to be one of the most promising of the batch, so good luck with this! Do you mind if I ask how you managed to get your first users on Brand.dev?

sheept - 9 hours ago

Does this respect llms.txt and robots.txt, or have you found it more effective if agents see what humans see?

bwm - 8 hours ago

Awesome! Been great watching this product improve so quickly, can't wait for what's next :)

debo_ - 6 hours ago

Remember when the Semantic Web attempted to make the entire web machine-readable?

https://en.wikipedia.org/wiki/Semantic_Web

kartik_malik - 8 hours ago

love the design... congrats

zuzululu - 9 hours ago

new frontier models do this already

asdev - 9 hours ago

So basically web scraping as a service with an API on top?

archerx - 9 hours ago

Great, another thing I have to block server side. Reminds me of the image leech protections that had to be in place because bandwidth was expensive. History doesn’t repeat but rhymes as they say.

seper8 - 9 hours ago

Seems wildly expensive, furthermore not a single mention of "ip" on homepage? Not using rotating ip's, residential proxies?

AKA unusable for high value data.

gokulrajaram - 8 minutes ago

[flagged]

Fno44 - 24 minutes ago

[flagged]

ryss20 - 7 hours ago

[flagged]

- 6 hours ago
[deleted]
laalshaitaan - 3 hours ago

lessgooo! context dev ftw!

badmonster - 8 hours ago

[dead]

growupdorks - 5 hours ago

[flagged]

cahaya - 8 hours ago

Nice, @grok how does it compare to Cloudflare that also provides a REST endpoint for structured markdown data and screenshots?