Table of Contents

Answers by Context.dev Investment Report

Answers by Context.dev Investment Report

Category: Web-data infrastructure / search and extraction API for AI applications

Company Stage: Seed-stage, early commercial

Founder or Founders: Yahia Bakour

Headquarters: San Francisco, California

Funding: Y Combinator S26; total funding not publicly disclosed

Business Model: Usage-based developer SaaS with self-serve and enterprise plans

Product Hunt Launch Date: September 20, 2026

Report Date: September 23, 2026

Investment Metric	Assessment
Venture Potential	72/100
Unicorn Path	Plausible
Valuation Attractiveness	Not Assessable
Evidence Confidence	63/100
Final Decision	DD

Executive Summary

Answers is a new Context.dev API that converts a research question into structured JSON with supporting URLs. It searches the web, reads relevant pages, and returns fields matching a developer-provided example schema. The product is intended for AI agents, internal research tools, data-enrichment systems, comparison products, and applications that otherwise need separate search, scraping, browser, and extraction infrastructure (launch announcement).

The underlying company is broader than this launch. Context.dev provides web scraping, crawling, search, structured extraction, website monitoring, screenshots, brand data, transaction enrichment, and SDKs through one API. It began as Brand.dev and subsequently expanded into general web-data infrastructure (official website; LinkedIn).

Product quality appears strong: the API is available, well documented, supports typed outputs and source URLs, and fits directly into automated workflows. Company quality also appears above average for its stage. Founder Yahia Bakour has relevant infrastructure experience, two prior startup exits, and Context.dev has entered Y Combinator’s S26 batch.

The strongest commercial signal is Context.dev’s company-reported base of more than 400 customers, 5,000 developers, and numerous detailed customer examples, including production workloads exceeding one million scrapes. These claims are more meaningful than Product Hunt votes, although revenue, payment status, retention, and customer concentration remain undisclosed (Y Combinator launch; customer library).

The largest concern is intense competition and limited structural differentiation. Search, scraping, browser execution, and LLM extraction are supplied by heavily funded competitors and can be combined from multiple vendors. The decision is DD: evidence supports formal diligence, but not investment without verified revenue, retention, gross margin, and round terms.

Product Overview

Developers send Answers a research task, an optional starting domain, and an example JSON structure. The service discovers sources, reads pages, and returns structured output plus a source list. Fast mode allows a 30-second research budget and costs 10 credits; Ultra allows 50 seconds and costs 100 credits. Failed research and timeout requests are not charged (API documentation; product announcement).

The product solves a recurring engineering problem: obtaining current web information normally requires search providers, browsers, proxies, anti-bot handling, parsers, retries, queues, and model-based extraction. Context.dev packages these components into one API.

The broader platform includes scraping, site mapping, batch processing, monitoring, brand/style-guide extraction, screenshots, product extraction, and transaction enrichment. SDKs and tooling are available for several programming languages through the company’s actively maintained GitHub organization.

Pricing is credit-based:

Free: 1,000 credits monthly.
Developer: $25 monthly for 10,000 credits.
Pro: $149 monthly.
Scale: $499 monthly for one million credits.
Enterprise: negotiated pricing for more than two million credits, security, procurement, and custom limits (pricing).

Answers therefore costs, before overages, approximately 1,000 Fast or 100 Ultra responses on the Developer plan. The service is API-based rather than a consumer mobile application.

Founder and Team Assessment

Founder Yahia Bakour previously worked in software engineering at Amazon and led engineering initiatives at Sunrun. He co-founded Stock Alarm, reportedly acquired by Center Mark Capital, and founded Essense.io, acquired by Optic. His background is highly relevant to reliable data ingestion, API development, and commercial developer products (founder profile; Acquire.com interview).

The founder reports that Stock Alarm reached more than 225,000 users and processed over 100,000 daily notifications. These figures are founder-reported, although the acquisition itself is corroborated by the founder’s public employment history.

Context.dev’s Y Combinator launch described a four-person team. LinkedIn also showed four associated employees, while Y Combinator’s company search subsequently described six employees. The discrepancy likely reflects timing or differences in counting, but current full-time headcount should be verified (Y Combinator; LinkedIn).

Public SDK development and open-source projects demonstrate sustained technical execution. Commercial capability is supported by prior startup sales and an extensive customer-reference program, although no sales-efficiency data are public.

Founder Assessment: Strong technical and founder-market fit with prior exit experience; current organization depth and commercial metrics require verification.

Market Opportunity

The initial segment is software companies building AI agents, enrichment products, monitoring tools, or automated research features that require production-grade public web data.

Context.dev reports more than 400 customers and 5,000 developers. Competitor-reported adoption indicates a substantially larger market: Firecrawl says more than 150,000 companies have used its platform, while Tavily says it is trusted by more than two million developers (Firecrawl; Tavily). These figures are company-reported and should not be interpreted as paying-customer counts, but they establish broad developer demand.

An illustrative bottom-up market scenario is:

25,000–100,000 production teams globally with recurring web-data requirements.
$6,000–$20,000 average annual revenue per team, combining self-serve Scale and enterprise usage.
Indicative annual addressable revenue: $150 million–$2 billion.

This is an analyst scenario, not a verified market forecast. Expansion opportunities include financial-data enrichment, sales intelligence, compliance monitoring, e-commerce intelligence, research automation, vertical datasets, and agent-native search. Demand timing is favorable, but the same growth is attracting well-capitalized competitors.

Traction and Growth Signals

The strongest traction evidence is the company’s claim of over 400 customers and 5,000 developers. Its customer library contains dozens of named implementation stories, including Mintlify, daily.dev, Similarweb, SiteGPT, and multiple early-stage AI companies (customer stories). Payment status and contract value are not disclosed, so these should be treated as product-usage references rather than verified commercial contracts.

Reported production examples include Bystreet completing more than one million scrapes, Slashy enriching approximately 5,000 companies daily, and Adapt monitoring around 6,000 websites. These are company-published customer statements and have not been independently audited.

The Product Hunt launch received approximately 199 points and ranked third on September 20, 2026. It was Context.dev’s third Product Hunt launch (Product Hunt; daily leaderboard). This represents launch visibility, not product-market fit.

GitHub shows active SDK updates and 21 public repositories, including TypeScript, Python, Ruby, Go, and PHP tooling. Several open-source demonstration projects have attracted more than 100 stars (GitHub).

Missing metrics are ARR, net revenue retention, paid customer count, usage growth, revenue concentration, gross margin, churn, and customer acquisition cost.

Traction Assessment: Meaningful early production usage and references, but financial traction remains unverified.

Competitive Position

Direct competitors include Firecrawl, Tavily, Exa, and Bright Data. Indirect alternatives include open-source crawlers, browser-automation frameworks, proxy providers, search APIs, and in-house extraction pipelines.

Context.dev’s principal differentiation is breadth under one developer interface: scraping, research answers, structured extraction, brand intelligence, monitoring, and transaction enrichment. The existing brand-data foundation may produce higher-quality company and visual enrichment than generic search APIs. Detailed documentation, SDK coverage, refunds for failed requests, and zero-data-retention options improve developer usability.

However, switching costs are initially low because API outputs are standard JSON or Markdown. Proprietary data assets and sustained accuracy advantages are not independently demonstrated. There is no direct network effect.

If the largest platform launched the same feature within six months, customers would continue using Context.dev only if it delivered consistently higher extraction success, lower latency, superior source coverage, or lower total cost. Customer stories suggest these advantages in selected workloads, but systematic benchmarks are unavailable.

Defensibility Assessment: Medium-Low

Business Model and Economics

Context.dev combines monthly subscriptions with metered overages and enterprise agreements. Public-plan ACVs range from $300 for Developer to $5,988 for Scale, before overage. Enterprise contracts could materially increase ACV.

Variable costs include search queries, proxy bandwidth, browser execution, CAPTCHA and anti-bot handling, storage, model inference, retries, and customer support. Answers adds search and LLM costs on top of the underlying page-retrieval stack.

Scale pricing implies about $0.0005 per credit before overage. An Ultra response consumes 100 credits, equating to roughly $0.05 of plan revenue, while a Fast response consumes 10 credits, or roughly $0.005, using fully consumed Scale-plan credits. Actual cost and margin per response are unknown.

Usage growth must generate revenue faster than infrastructure and model costs. Gross margin should be examined by endpoint because basic cached scraping may be highly profitable while browser-heavy research may be materially less attractive.

Unicorn Path

Assume a 10× ARR multiple, appropriate only for a fast-growing infrastructure company with strong net retention and software-like gross margins.

Required ARR = $1 billion ÷ 10 = approximately $100 million.

Equivalent customer requirements include:

Approximately 333,000 Developer accounts at $300 annual revenue.
Approximately 56,000 Pro accounts at $1,788 annual revenue.
Approximately 16,700 Scale accounts at $5,988 annual revenue.
Approximately 2,000 enterprise customers at an assumed $50,000 ACV.

A realistic path would require a blended self-serve and enterprise model, expansion from scraping into recurring monitoring and data infrastructure, high usage-based net retention, and durable performance advantages. The company would also need international scale, larger enterprise contracts, and substantially expanded engineering and sales teams.

Competitor financing demonstrates investor belief in the category: Firecrawl announced a $14.5 million Series A, while Tavily announced $25 million in total funding, including a $20 million Series A (Firecrawl; Tavily).

Unicorn Path: Plausible

Valuation Assessment

Y Combinator S26 backing is verified through both Context.dev and Y Combinator. No reliable public information was found concerning additional investors, total capital raised, valuation, SAFE cap, or current round terms.

Valuation Attractiveness: Not Assessable

Assessment requires current ARR, growth, gross margin by endpoint, net revenue retention, customer concentration, burn, runway, cap table, prior SAFEs, round size, post-money valuation, and liquidation preferences.

Key Risks

Rapid commoditization of search, scraping, and structured extraction.
No publicly verified revenue, retention, or gross-margin evidence.
Well-funded competitors with much larger reported developer reach.
High and variable costs for browser-heavy and multi-source research.
Dependence on changing website structures and anti-bot systems.
Copyright, database-rights, robots.txt, and platform-terms exposure.
Low API switching costs unless performance is materially superior.
Customer concentration risk among AI startups and YC-adjacent companies.
Source lists are not field-level citations, limiting auditability for sensitive use cases.
Legal terms still describe the narrower brand-data product and broadly restrict automated access, creating documentation ambiguity for an API designed for automation (terms).

Final Assessment

Venture Potential: 72/100

Category	Score
Market Size and Expansion Potential	18/20
Traction and Growth Evidence	13/20
Founder and Team	13/15
Product Strength	8/10
Distribution Potential	10/15
Business Model and Economics	6/10
Defensibility	4/10
Total	72/100

The strongest elements are founder quality, market timing, product breadth, and numerous production references. The weakest are competitive defensibility and the absence of verified financial and retention data.

Evidence Confidence: 63/100

Verified evidence includes legal entity, pricing, API documentation, public repositories, YC participation, security posture, and founder history. Customer counts, developer counts, workloads, and performance improvements are company-reported. Revenue, margins, retention, cap table, burn, and valuation remain unavailable.

Final Decision: DD

Context.dev has sufficient founder quality, market opportunity, product maturity, and referenceable usage to justify formal diligence. Investment cannot be recommended until revenue quality, cost structure, retention, financing terms, and differentiation against larger competitors are verified.

Upgrade Conditions

Verified ARR above $1 million with strong sequential growth.
Net revenue retention above 120% and low logo churn among production customers.
Gross margin above 70%, including Answers and browser-heavy requests.
Multiple enterprise contracts above $50,000 ACV.
Independent benchmarks showing superior extraction success or cost.
Reduced dependence on startup and YC-adjacent customers.
Updated API-specific commercial terms and clear data-retention commitments.

Downgrade Conditions

Usage does not convert into paid production accounts.
Gross margin deteriorates as Answers usage scales.
Material customer migration to larger competing APIs.
Legal or platform enforcement restricts important data sources.
Reliability failures in customer-critical workflows.
Customer concentration or churn materially exceeds expectations.

Questions for Further Diligence

What are current ARR, MRR, and monthly net-revenue growth?
Of the reported 400 customers, how many are paying and active in production?
What are 30-, 90-, and 180-day retention and net revenue retention?
What percentage of revenue comes from the ten largest customers?
What is gross margin by Scrape, Answers, Extract, Brand, and Monitor endpoints?
How do Fast and Ultra accuracy, latency, and cost compare with competitors?
What are self-serve conversion, CAC, payback, and primary acquisition channels?
How many customers have signed enterprise contracts, and what is median ACV?
What proprietary data, routing, or evaluation systems create sustainable differentiation?
What are team composition, monthly burn, and runway?
What are the cap table, current valuation, round size, and financing terms?
How does the company manage copyright, robots.txt, source licensing, and platform-access risks?