Scraping APIs bill you twice: once for the page, again for the AI that reads it. We bought GPUs instead - so TheCrawler scrapes any site to clean JSON/markdown with AI extraction INCLUDED. 1 credit = 1 page, no per-call AI surcharge, structurally impossible for metered rivals to match. Grounded extraction returns null instead of inventing values. Plus web search, async batch + webhooks, change-monitoring, and an MCP server for Claude Code/Cursor. 500 free pages, no card.
No reviews yetBe the first to leave a review for TheCrawler
Maker
š
Hi Product Hunt š I'm Manchit, and I built TheCrawler because scraping APIs bill you twice ā once for the page, again for the AI that reads it. Their marginal cost is an OpenAI invoice, so they meter every extraction. I bought GPUs instead (128GB box running a Qwen MoE via llama.cpp). Extraction became a sunk cost, so I price it like a plain scrape: 1 credit = 1 page, AI included. That's the whole pitch ā the rarest thing here isn't a feature, it's the cost structure. A metered competitor can't match it without re-architecting their COGS.
What it does: scrape any URL to markdown/JSON (+ brand data, contacts, tables) Ā· AI extraction to your schema with a grounding validator ā every value must trace to the page text or it returns null instead of inventing Ā· you only pay for valid results: /diagnose scores extractability before you spend a credit, and failed/empty extractions are auto-refunded Ā· bring your own LLM ā point extraction at any OpenAI-compatible endpoint (Ollama, llama.cpp, LM Studio) and your data never leaves your infra Ā· web search Ā· async batch with signed webhooks Ā· change-monitoring watchlists Ā· an MCP server so it works inside Claude Code and Cursor.
Honest limits: no stealth/residential-proxy tier yet (heavily bot-protected sites will block it), answer-synthesis search is on the roadmap, MCP is stdio-only.
Free tier is 500 pages, no card. I'd genuinely love your teardown - I'll be here all day answering everything.
Report
Maker
Hey Product Hunt š Manchit here, maker of TheCrawler.
I built this because every scraping API I used billed me twice ā once to fetch the page, then again in AI credits for the model that reads it. Those extraction bills were unpredictable and grew faster than my actual usage.
So I did the unreasonable thing and bought the GPUs. TheCrawler runs the extraction model on hardware we own ā so structured JSON extraction is part of the scrape, not a separate metered line item.
What you get:
⢠One call: URL in ā clean markdown or validated JSON out
⢠Page-grounded extraction ā it returns null for anything it can't verify on the page, instead of inventing values
⢠A drop-in MCP server (claude mcp add) for AI agents, plus LangChain / LlamaIndex
⢠500 free pages to try, no card required
It's day one and I'm here all day ā genuinely want your feedback, edge cases, and "does it handle X?" questions. Throw a gnarly page at it; if it chokes, tell me and I'll fix it.
Hey Product Hunt š Manchit here, maker of TheCrawler.
I built this because every scraping API I used billed me twice ā once to fetch the page, then again in AI credits for the model that reads it. Those extraction bills were unpredictable and grew faster than my actual usage.
So I did the unreasonable thing and bought the GPUs. TheCrawler runs the extraction model on hardware we own ā so structured JSON extraction is part of the scrape, not a separate metered line item.
What you get:
⢠One call: URL in ā clean markdown or validated JSON out
⢠Page-grounded extraction ā it returns null for anything it can't verify on the page, instead of inventing values
⢠A drop-in MCP server (claude mcp add) for AI agents, plus LangChain / LlamaIndex
⢠500 free pages to try, no card required
It's day one and I'm here all day ā genuinely want your feedback, edge cases, and "does it handle X?" questions. Throw a gnarly page at it; if it chokes, tell me and I'll fix it.
Thanks for checking it out š·ļø