ScrapingBee through Squiid

What ScrapingBee is

ScrapingBee is a single-request scraping API. You pass a URL and options, and it chooses a proxy, renders the page in a headless browser if needed, waits for selectors, executes custom JavaScript, takes a screenshot, or extracts fields with CSS rules, then returns the result. Premium and residential proxies with country targeting handle sites that block datacenter IPs, and a Google search endpoint returns results as JSON. Concurrency is set by plan, so a batch job has a known ceiling on how fast it can work through a queue.

For AI-coded apps its appeal is simplicity: one HTTP call replaces a browser, a proxy pool and a retry strategy. It is the right tool when you need a moderate number of pages from sites that do not want to be read automatically, for example price checks, availability monitoring, or pulling a partner's page into your app because they have no API. It also has a simpler mental model than a browser platform, which is an advantage when an agent is writing the integration unattended.

Why connect it through Squiid

ScrapingBee is on the Squiid roadmap. When it is connected, requests will go to https://api.squiid.io/v1/scrapingbee/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention), and API credits will meter against prepaid credits at ScrapingBee's listed price on one invoice. Because rendering and premium proxies cost more credits per request than a plain fetch, the per-day spend view is where you find out which option your agent chose by default. Failed requests are not charged under the provider's listed terms, which keeps a blocked target from quietly consuming your balance.

• One account, one key, one bill, one dashboard. ScrapingBee sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the ScrapingBee credentials. Your code carries SQUIID_API_KEY, so SCRAPINGBEE_API_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what ScrapingBee costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• One-call scraping with proxy rotation
• JavaScript rendering and screenshots
• Country targeting and premium proxies
• CSS-rule extraction to JSON
• ScrapingBee list pricing, no markup

How to connect ScrapingBee

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces SCRAPINGBEE_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/scrapingbee/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

ScrapingBee charges API credits per request, with rendering and premium proxies costing more credits, on plan tiers at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of ScrapingBee usage, with no markup and no per-request margin.

ScrapingBee has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so ScrapingBee usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: ScrapingBee is usage-metered, so leaving means creating your own ScrapingBee key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks ScrapingBee's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

ScrapingBee through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on ScrapingBee usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.