Cycling through all six. Tap any point to stop.

Measured on six things

Web scraping API that turns any URL into HTML, text, Mark...

Growth

Real problem, four named segments, and a concrete wedge: ScrapingBee-compatible params at 38–40% less with a recurring free tier. Differentiated but in a crowded, price-sensitive category.

Screenshots

1 / 1

Webfetch

About this app

I've spent enough time stitching together headless browsers, proxy pools, and custom parsers to know that scraping is usually 20% creative problem-solving and 80% babysitting infrastructure. Webfetch.io is one of those tools that quietly removes the boring 80%. It's a web scraping API that takes a URL plus a handful of parameters and hands back exactly the shape you want: rendered HTML, clean plain text, LLM-friendly Markdown, screenshots, or structured JSON defined through CSS/XPath extract_rules. Under the hood it runs headless browsers, rotating datacenter and ISP proxy exits, and browser actions (js_scenario) for click-and-scroll flows — all behind one endpoint. The part I genuinely appreciate is the honesty of the billing: failed fetches cost zero, and the mode=auto escalation ladder climbs cheaper routes first and only bills the one that worked. The free tier isn't a stingy trial either — 1,000 credits up front, then 250 every month with no card. For anyone building price moni...

Key features

1One endpoint returning rendered HTML, clean text, Markdown, screenshots, or JSON via CSS/XPath extract_rules.
2ScrapingBee-compatible parameter names, defaults and credit costs — migration is a base URL and a key.
3Recurring free tier: 1,000 credits then 250/month banking to 1,000, no card, failed fetches never billed.

Target customer profile

Drawn from the product itself, not from a survey.

Demographic

Backend and data engineers building scraping/ETL pipelines

Pain points

Proxy management, headless browser infra, and parser maintenance eat dev time

Primary needs

One reliable API endpoint with structured JSON extraction and predictable credits

Demographic

AI/ML teams building LLM and RAG ingestion workflows

Pain points

Raw HTML is noisy; cleaning and chunking pages for retrieval is fiddly

Primary needs

Clean Markdown output via return_page_markdown plus SDK and MCP support

Demographic

E-commerce and market analysts running price/stock monitoring

Pain points

Retail pages are JS-heavy and defended against bots

Primary needs

render_js with extract_rules, stealth proxies, and scheduled JSON output

Demographic

Growth and SEO teams aggregating search and directory data

Pain points

SERP data is fragmented across engines and gated behind scraping effort

Primary needs

Multi-engine Search API (Google, Bing, Yahoo, Brave) returning JSON/CSV

Scout Review

Written by AI from measured evidence, scored out of 100.

Webfetch is a web scraping API that does the boring parts well: one endpoint, ScrapingBee-compatible parameters, headless rendering, rotating proxies, CSS/XPath extraction, and Markdown output for LLM pipelines. The site is fast (97 mobile Lighthouse), the security headers are complete (13/13), and the free tier is recurring rather than a trial. The docs are unusually thorough for an indie tool, and the keyless live demo is a genuinely good onboarding move. Where it falls short: accessibility has three real Lighthouse failures and no conformance statement, there's no SOC 2 or bug bounty for enterprise buyers, and the growth story is 'cheaper ScrapingBee' rather than a structural advantage. A competent, well-executed tool in a crowded market.

Measure by measure

Usability

Email + six-digit code signup, key on screen, no card. Full parameter table in docs, ScrapingBee migration guide, and a keyless live demo that runs a real scrape. Onboarding is genuinely short.

Design

Terminal-first landing page with real curl examples and Wf-Cost headers — deliberately developer-flavored and consistent across home, docs and pricing. Dense but coherent; no stock-photo filler.

Speed

Lighthouse 97 mobile / 100 desktop, LCP 1.0s, CLS 0. The site itself is fast, and the API advertises 38ms raw / 412ms rendered latencies in its own demo output.

Security

13/13 header checklist: HSTS, CSP, frame protection, secure cookies, SPF, DMARC. robots.txt honored by default, hosts pinned and re-validated on redirect, banks/payment processors blocked. No SOC 2 or bug bounty found.

Accessibility

Lighthouse 92/100 with three real failures: insufficient color contrast, non-sequential heading order, and links distinguishable only by color. No WCAG statement or a11y page found.

Growth

Real problem, four named segments, and a concrete wedge: ScrapingBee-compatible params at 38–40% less with a recurring free tier. Differentiated but in a crowded, price-sensitive category.

Improvement areas

No SOC 2, ISO 27001, or bug bounty program surfaced — blocks enterprise procurement.
Three Lighthouse accessibility failures (contrast, heading order, color-only links) and no WCAG statement.
Free-tier requests can return 503 under paid load, per the pricing page's own admission.
Growth positioning is price-led rather than structural — vulnerable to incumbent price matching.

Design & Usability

Webfetch's design is unapologetically developer-first: the hero is a curl command with real Wf-Cost headers, and the same terminal aesthetic carries through docs and pricing. It's dense — five sections of feature copy stacked on one page — but coherent, and there's no stock photography or fake testimonials anywhere. Usability is the stronger half. Signup is an email and a six-digit code with the key rendered on screen, no card. The docs ship a full parameter table with types and defaults, a ScrapingBee migration guide, and a keyless live demo that runs an actual scrape against any URL you give it. The free tier is recurring (1,000 then 250/month, banking to 1,000) rather than a one-time trial, which is a real differentiator against ScrapingBee. The one blemish: free-tier requests can return a 503 under paid load, which the pricing page admits in plain text.

Speed & Security

Speed is the standout. Lighthouse scores 97 mobile and 100 desktop with LCP at 1.0s and CLS at zero — the marketing site is genuinely snappy, and the API advertises 38ms raw / 412ms rendered latencies in its own demo output. Security is solid on the technical layer: the HTTP probe returned 13/13 checklist points including HSTS, CSP, frame protection, secure cookies, SPF and DMARC. The docs add real substance — robots.txt honored by default, hosts resolved and pinned before a byte is sent and re-checked on every redirect, and a proxy network that refuses banks, payment processors and some government services on every plan. What's missing is the compliance layer: no SOC 2, ISO 27001, or bug bounty program surfaced in the collected evidence. For an indie API that's normal, but it caps the score below the enterprise tier.

Accessibility & Growth

Accessibility lands at 68: Lighthouse scores 92/100, but three real failures remain — insufficient color contrast, non-sequential heading order, and links distinguishable only by color. There's no WCAG conformance statement or accessibility page, and no multi-language support mentioned. Growth is the more interesting question. The problem is real (scraping infra is 80% babysitting), the target segments are specific (backend engineers, LLM/RAG teams, price monitors, SEO teams), and the wedge is concrete: ScrapingBee-compatible parameter names, defaults and credit costs at 38–40% lower pricing with a recurring free tier instead of a one-time trial. Against Firecrawl, the pitch is Markdown output plus SDKs and an MCP server. That's a legitimate differentiator, but it's a price-and-compatibility wedge in a crowded category where the incumbents can match on features and the buyer can switch on a base URL change. It can grow; it just has no structural moat.

Conclusion

If you're building a scraping pipeline and you've already written ScrapingBee-shaped code, Webfetch is a one-line base URL swap that cuts your bill by roughly 40% and gives you a free tier that doesn't expire. That's a real offer. If you need SOC 2 paperwork, an accessibility commitment, or a moat that survives ScrapingBee matching your price, look elsewhere — or at least budget for the migration back.

Suggestions for improvement

Publish a SOC 2 Type II report or at minimum a security page with pen-test summary and responsible disclosure policy.
Fix the three Lighthouse accessibility failures: contrast ratios, heading order, and link styling beyond color alone.
Add an accessibility statement and WCAG 2.1 AA conformance target — cheap credibility for a developer tool.
Address the free-tier 503 under load with a queue or retry-after header so free users don't hit a wall mid-integration.

How we score

Alternatives comparison

Named competitors, point by point. Nobody paid to appear here or to be left out.

	Webfetch	ScrapingBee	Firecrawl
Free tier	1,000 credits then 250/month recurring, banking to 1,000, no card	1,000 credits one-time trial	Limited free credits, tiered plans
Starting paid price	$11.99/mo for 75,000 credits	~38–40% higher per Webfetch's own comparison	Free tier plus paid plans priced per credit
ScrapingBee parameter compatibility	Yes — names, defaults and credit costs match; base URL swap	Native (the original)	No — different API surface
Markdown output for LLM/RAG	return_page_markdown=true, plus SDK markdown() and MCP fetch_page	Not a primary feature	Core feature — primary positioning
Structured JSON extraction	extract_rules with CSS or XPath selectors	extract_rules with CSS/XPath	Schema-based extraction
Failed fetches billed	Never — billing on success only	Not stated as free	Not stated as free