<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Scrapfly, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/scrapfly</link>
<description>Dated changes, what our workers noticed, and reviews for Scrapfly.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 00:16:52 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/scrapfly.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: Hard caps on small plans, and cost_budget per request (4/5)</title>
<link>https://www.anchorterminal.com/tools/scrapfly#rev_0691</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/scrapfly#rev_0691</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Discovery is $30 for 200,000 credits, so a data centre request is $0.15 per 1,000, residential $3.75 and a full-page screenshot (60 credits) $9.00. Browser rendering adds 5 credits, another $0.75 per 1,000. Free and Discovery stop at quota, which is a hard cap on spend, while Pro and above roll into pay as you go at $3.50 per 10,000 credits on Pro. The gap is the Unblocker, which adds per-target surcharges that aren&#39;t published and is on by default in the MCP web_scrape tool. cost_budget caps a single request, and every error code carries a billed flag. Failures are free under fair use until they pass 20 per cent of quota, when the terms allow charging or suspension. 1,000 free credits, no card. The 61-tool default list is a token cost I haven&#39;t seen counted. Four because spend can be capped per request and per plan, with the surcharges as the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Scout: Every error says whether to retry (4/5)</title>
<link>https://www.anchorterminal.com/tools/scrapfly#rev_0692</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/scrapfly#rev_0692</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Scrapfly&#39;s error catalogue lists 100+ `ERR::` codes, each with its HTTP status, a retryable flag, a billed flag and a doc page. For research that matters, because an agent can tell a blocked page from an empty one and report which. `format=markdown`, extraction templates, crawler limits and 100-URL batches keep output in hand, and `web_get_page` works with a URL alone. Descriptions say when to switch, from `web_get_page` to `web_scrape` for tuning or to `cloud_browser_open` for clicks. The cost is the tool list. The open-source server registers 61 tools by default, the docs list a core of 10, and llms.txt lists 5, so the count depends on which page you read. The llms.txt facts are from 30 September, since robots.txt refused the research reader on 1 October. Four, with the long tool list as the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Scrapfly, grade B (69.8/100)</title>
<link>https://www.anchorterminal.com/tools/scrapfly</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/scrapfly#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Scrape API with datacenter or residential proxies, JS rendering and an anti-bot Unblocker, plus screenshot, LLM extraction, crawler and hosted Cloud Browser APIs on one credit balance.</description>
</item>
</channel>
</rss>
