DLBrowser gives AI agents reliable web access in one line. A self-healing engine escalates through 5 backends to beat Cloudflare, captchas & JS-heavy pages — with per-run cost tracking and transparent credits. MCP-native, MIT, self-hostable. Works with Claude, Cursor, Windsurf & more.
No reviews yetBe the first to leave a review for DLBrowser
Maker
📌
Hi Product Hunt 👋
I built DLBrowser after wiring web access into one too many AI agents and hitting the
same wall: some sites work with a plain fetch, others need a full browser, others are
behind Cloudflare — and the built-in agent browser tools fail silently while you have
no idea what each run costs.
DLBrowser is one MCP endpoint (plus a Python package + CLI) backed by a self-healing
engine. It tries the fastest backend first and only escalates to heavier, stealthier
ones when a site actually blocks you — recording the backend, credits, and estimated
cost of every run.
Report
finally tried it with a stubborn cloudflare page and it actually pushed through on the third backend without me babysitting it. the per-run cost line is genuinely useful for keeping my agent spend in check.
Report
honestly the cost tracking per run is a nice touch, but it would be super useful to have a built-in retry budget or fallback summary so you know which backend actually succeeded and how many credits got burned along the way when things go sideways.
Report
Finally something that doesn't choke on the first Cloudflare wall it hits, the multi-backend fallback actually worked on a stubborn site I'd been scraping manually for days.
Report
The per-run cost tracking sounds super useful. One thing I'd love to see is a simple shared cache layer so if multiple agents hit the same page within a short window they don't each pay for a fresh fetch, would cut costs noticeably for teams running parallel agents on overlapping research.
Report
the self-healing backend escalation is genuinely clever, finally stopped fighting captchas in my agent loops
Report
Honestly, the per-run cost tracking is a nice touch since most tools like this just hand you a bill at the end. Also cool that it actually falls back through multiple backends instead of just giving up on a stubborn page.
finally tried it with a stubborn cloudflare page and it actually pushed through on the third backend without me babysitting it. the per-run cost line is genuinely useful for keeping my agent spend in check.
honestly the cost tracking per run is a nice touch, but it would be super useful to have a built-in retry budget or fallback summary so you know which backend actually succeeded and how many credits got burned along the way when things go sideways.
Finally something that doesn't choke on the first Cloudflare wall it hits, the multi-backend fallback actually worked on a stubborn site I'd been scraping manually for days.
The per-run cost tracking sounds super useful. One thing I'd love to see is a simple shared cache layer so if multiple agents hit the same page within a short window they don't each pay for a fresh fetch, would cut costs noticeably for teams running parallel agents on overlapping research.
the self-healing backend escalation is genuinely clever, finally stopped fighting captchas in my agent loops
Honestly, the per-run cost tracking is a nice touch since most tools like this just hand you a bill at the end. Also cool that it actually falls back through multiple backends instead of just giving up on a stubborn page.