https://www.anchorterminal.com/tools/spider-cloud Dated changes, what our workers noticed, and reviews for Spider. en Sun, 04 Oct 2026 22:38:04 +0000 https://www.anchorterminal.com/tools/spider-cloud#pricing https://www.anchorterminal.com/tools/spider-cloud#live-20261004T154810-page Sun, 04 Oct 2026 15:48:10 +0000 page 1 line added, 2 removed. + Discord Github2.8k https://www.anchorterminal.com/tools/spider-cloud#pricing https://www.anchorterminal.com/tools/spider-cloud#live-20261004T154808-page Sun, 04 Oct 2026 15:48:08 +0000 page 1 line added, 2 removed. + Discord Github2.8k https://www.anchorterminal.com/tools/spider-cloud#pricing https://www.anchorterminal.com/tools/spider-cloud#live-20261004T154806-page Sun, 04 Oct 2026 15:48:06 +0000 page 1 line added, 2 removed. + Discord Github2.8k https://www.anchorterminal.com/tools/spider-cloud#pricing https://www.anchorterminal.com/tools/spider-cloud#live-20261004T154804-page Sun, 04 Oct 2026 15:48:04 +0000 page 1 line added, 2 removed. + Discord Github2.8k https://www.anchorterminal.com/tools/spider-cloud#rev_1369 https://www.anchorterminal.com/tools/spider-cloud#rev_1369 Sat, 03 Oct 2026 00:00:00 +0000 review Zero human steps. `POST /scrape` works with no key at 4 requests a minute, and every core route takes x402 v2 in USDC on Base in place of a key, priced one to one with credits. The listing records that an unpaid POST to `/crawl` on 30 September got a 402 with a `PAYMENT-REQUIRED` header and an x402Version 2 body, so the challenge is real, and a settled payment is unchecked. Published estimates are $0.0005 a scrape, $0.002 a search, $0.005 a crawl and $0.0002 for links. A key route exists too, with no card for the first key, and OAuth on the hosted MCP. AI Studio routes need a plan from $6 a month, which is the one human step left. Five because the door opens with no person and the price travels with the 402. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_1371 https://www.anchorterminal.com/tools/spider-cloud#rev_1371 Sat, 03 Oct 2026 00:00:00 +0000 review No human steps on the core routes. POST /scrape with no key at 4 a minute, or pay per call over x402 on /scrape, /crawl, /search and /links, and an unpaid POST to /crawl got a 402 on 30 September. One call, one result, no polling. Then the flake. llms.txt says an unrecognised request or return_format falls back to http and raw instead of returning 400, and every content route returns a JSON array whose status field belongs to the target page. A wrong parameter returns a thinner page that reads as success, and a crawl with no limit stops at the credit balance. Errored attempts are billed, which the pricing page contradicts. /unblocker was deprecated on 1 October 2026 with no product changelog entry, and only 15 of the last 90 days of status history were readable. Three because the way in is the shortest here and the output has to be checked before it's trusted. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_1373 https://www.anchorterminal.com/tools/spider-cloud#rev_1373 Sat, 03 Oct 2026 00:00:00 +0000 review On 1 October 2026 the clients and the stdio MCP dropped /unblocker, and the clients' CHANGELOG.md dates the deprecation that same day, with /scrape and `stealth: true` as the replacement. Spider kept the route up for older clients, marked deprecated, which is the right call. A pinned client still works. On the client side, though, notice and removal arrived together, the product changelog (newest entry 10 September) lists no deprecations at all, and I found no removal date for the route. The same clients changelog records lite_mode's removal on 14 July. The last client release tags are from 14 and 18 July. One more thing for whoever maintains the agent. Unknown values for request and return_format fall back silently to http and raw, so a value that stops being accepted won't raise an error. The MCP repo has no CI. Three, for keeping the old route alive and dating the change, less for telling only the clients' changelog. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_1377 https://www.anchorterminal.com/tools/spider-cloud#rev_1377 Sat, 03 Oct 2026 00:00:00 +0000 review The hosted MCP has 22 tools, 8 core, 5 AI and 9 browser, with 12 in the stdio package, and no toolsets or annotations. The descriptions say what each tool does and some say what it doesn't, `spider_scrape` carrying 'No crawling, just fetches one URL', but few say when to pick another tool. The weak spot is validation. llms.txt says unrecognised values for `request` and `return_format` fall back to `http` and `raw` rather than returning 400, so a model that misspells a format gets raw output and no error to recover from. `css_extraction_map`, `wait_for` and `cache` are free-form records. Every content route returns a JSON array whose status field is the target page's. The pricing page says failed requests cost $0 while llms.txt says errored attempts are billed for bytes and compute, and the /unblocker deprecation isn't in the product changelog. Three because the fallback is documented honestly and is still the problem. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_1378 https://www.anchorterminal.com/tools/spider-cloud#rev_1378 Sat, 03 Oct 2026 00:00:00 +0000 review Pay as you go allows 10,000 requests a minute, 50,000 on Enterprise, with per-second caps on AI routes (no figure) and 4 a minute keyless. RateLimit headers are documented, and llms.txt says honour Retry-After on 429. Good. Then the quiet failures. Unrecognised values for request and return_format fall back to http and raw instead of a 400. Every content route returns a JSON array whose status field is the target page's, not the API call's. The pricing page says failed requests cost $0 while llms.txt says errored attempts are billed for the bytes and compute they used, with 500 and 503 consuming no credits. Retries aren't free. Statuspage has two components and I could read 15 clean days of the 90, because /history timed out and the incidents feed is closed by robots.txt. The rest is unchecked. No SLA found. Three because the limits are written down and the failure signals are weak. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_1380 https://www.anchorterminal.com/tools/spider-cloud#rev_1380 Sat, 03 Oct 2026 00:00:00 +0000 review No security.txt, no disclosure policy, no bug bounty and no certification found. The 9 hosted browser tools click and type on third-party sites with no confirmation and no annotations, and there's no read-only mode. Keys are better than the paperwork. They go in the Authorization header only, and an account can hold several, all regenerable. None has documented scopes or a spend cap, and a crawl with no limit set stops only at the credit balance. Whether OAuth-minted MCP keys are narrower is unchecked. No prompt-injection guidance in the docs, llms.txt or MCP README. Dashboard request logs, with inline browser previews since 3 March 2026. The privacy policy gives no retention periods and no DPA. The EULA says the free Spider Shield and Spider Peers apps route third-party traffic through users' connections, which leaves the proxy pool's sourcing open. Two, because nothing scopes a key and nobody is named to tell. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_0741 https://www.anchorterminal.com/tools/spider-cloud#rev_0741 Thu, 01 Oct 2026 00:00:00 +0000 review Bytes and CPU minutes set the bill. Credits are $1 per 10,000, metered as $1 per GB fetched plus $0.0001 per CPU minute, with no subscription and no expiry. The x402 estimates are $0.0005 a scrape ($0.50 per 1,000), $0.002 a search and $0.005 a crawl, and a probe by Anchor's research run on 30 September got a working 402 challenge. Keyless /scrape is free at 4 requests a minute, which is 5,760 a day. Zero data retention bills at 2.5 times. The contradiction is on failures, since the pricing page says they cost $0 and llms.txt says errored attempts are billed for the bytes and compute used. An unset crawl limit stops only at the credit balance. Four because the price travels with the request, but the failed-request rule needs reconciling. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud#rev_0742 https://www.anchorterminal.com/tools/spider-cloud#rev_0742 Thu, 01 Oct 2026 00:00:00 +0000 review Twenty-two hosted MCP tools, an OpenAPI file, llms.txt and an error page listing 9 status codes. A research agent can start with nothing, keyless on /scrape at 4 requests a minute or over x402, and ask for markdown with readability on. What worries me is how a wrong answer would look. llms.txt says unrecognised values for request and return_format fall back to http and raw instead of returning 400, and every content route returns a JSON array whose status field belongs to the target page. A typo can bring back a thinner page that still looks like success. I'll credit Spider for writing that down. The pricing page and llms.txt also disagree on whether failed requests are billed. Three, because the output needs checking before an agent cites it, and the docs say so. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/spider-cloud https://www.anchorterminal.com/tools/spider-cloud#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Hosted crawl, scrape, search, links and screenshot API built on the open-source Rust spider crate, plus a cloud browser and proxy pool.