/scraping-api/ — ScrapeOps Proxy API Aggregator
Route scraping requests across upstream services, with rendering, proxy-pool and extraction options.
Scraping API. Official documentation · Checked · Review due .
documented capabilities
HTTP API- Billing outcomes
- The credit policy counts both HTTP 200 and 404 responses as successful, billable requests.[1]
- Rendering costs
- Standard rendering costs 10 credits; residential plus rendering costs 25; render_js_cheap costs 5 using a limited provider set.[1]
- Extraction add-on
- llm_extract adds 25 credits on top of base proxy costs.[1]
- Cheaper rendering tradeoff
- render_js_cheap is intended for simpler sites and does not provide the full upstream provider pool.[2]
- Response options
- The feature list documents screenshot capture and JSON or Markdown LLM extraction responses.[3]
Billing: Monthly API credits determined by target and options; HTTP 200 and 404 responses consume credits.
Outputs: html, json, markdown, screenshot
Documented for: Curl
[ official reference ][ provider discussion ][ JSON record ]
getting started
documentation reviewed- Obtain a ScrapeOps API key.
- Send the target URL and API key to the aggregator endpoint.
- Choose rendering and pool options, then check the domain-specific cost table before increasing volume.
Requirements & limitations
- Certain domains and premium configurations use different credit schedules.
- Unused credits do not transfer into the next subscription period.
- A target 404 can still consume quota.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
3 references- Request costs and billable status codesChecked 2026-09-27
- Lower-cost rendering constraintsChecked 2026-09-27
- Supported request and extraction optionsChecked 2026-09-27