Skip to content

Image Search Results via a Single Scraping Call

Image search pages are awkward to collect: the grid is rendered by JavaScript, lazy-loads as you scroll, and sits behind bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains what a hosted image-results API returns, which request options change the output, and how credits are consumed — so you can size a pipeline before writing code.

What one call returns

Send a URL for an image search results page and the service renders the page's JavaScript, rotates residential proxies, and returns rendered HTML ready to parse. With extraction configured, the response comes back as parsed JSON. Each image search results page yields the image URL, the source page URL, image dimensions, alt text, and references to visually-similar matches. That field set is the same across the major image search engines the service covers.

Three workflows teams actually run

Most image-SERP pipelines fall into one of three shapes:

  • URL harvesting — collect image URLs to spot emerging visual trends and feed a market-insight dataset.
  • Product image detection — track competitor product imagery alongside pricing signals.
  • Object-category classification — enrich training or analysis datasets by grouping images into categories.

Each of these needs the same core fields; the difference is downstream (deduplication, matching, or model input) rather than in the request itself.

Field map: what you get and what it's for

If you need a different shape, extract_rules maps CSS selectors to your own field names, and ai_extract_rules accepts a natural-language spec instead of selectors. Both return parsed JSON.

Request options that change the result

Four options matter most for image SERPs:

  • render_js — executes page JavaScript; required for lazy-loaded image grids.
  • stealth_proxy — routes through stealth proxies to get past CAPTCHA and bot checks.
  • country_code — geo-targets the request so results reflect a specific market.
  • js_scenario — scrolls image grids, clicks "load more" triggers, and waits for lazy-loaded data before capture.

For LLM pipelines, the same pages can be returned as clean Markdown. For no-code workflows, the API plugs into n8n automation without writing scraper code.

Worked credit example

Per-request credit cost depends on which options you enable. The published per-request figures for each configuration are:

  • Base request: 1 credit.
  • With render_js: 5 credits.
  • With premium proxies and JS rendering: 25 credits.
  • With stealth_proxy: 75 credits.

Each figure is the total cost of a request in that configuration, not a separate line item to be summed. So a batch of 1,000 image-SERP pages rendered with JS and stealth proxies consumes roughly 75,000 credits — which is the entire Hobby plan allowance. A batch of 1,000 pages with plain JS rendering consumes about 5,000 credits. Size your plan against the option mix, not the raw page count.

Three failure modes, three fixes

When image-SERP collection breaks, the cause usually falls into one of three buckets:

  1. Your concurrency limit — the API enforces concurrency per plan, not per-target rate limits. If you hit it, requests queue or fail; the fix is a higher-concurrency plan or a smaller in-flight batch.
  2. Target-side throttling — the image search engine itself may throttle aggressive patterns. Space out requests or spread them across multiple sessions.
  3. Bot detection — if pages come back blocked or empty, enable stealth_proxy and confirm render_js is on so the grid actually loads.

Distinguishing these early avoids tuning the wrong knob.

Setup path

  1. Create an account to get an API key and free trial credits.
  2. Install the SDK for your stack (Python, Node.js, Go, PHP, Ruby, or Java) — or use plain cURL.
  3. Send a GET request with the API key and any image search URL.
  4. Add advanced parameters only when you need them: render_js, stealth_proxy, country_code, ai_extract_rules.

Code samples exist per language; the dashboard request builder generates a snippet you can drop into your codebase.

Plans and what changes between them

Standard plans run from Hobby through Business +; enterprise tiers extend credits and concurrency further. Every plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules. Priority email support, a dedicated account manager, and team management appear only on Business and above. The full plan matrix — credits, concurrency, and feature inclusion per tier — is rendered from the pricing module below; consult it for exact figures rather than relying on any summary here.

Compliance and legal notes

Public-facing pages can usually be collected, but always review the target site's terms of service before deploying and avoid post-login content. The service does not collect or store personal data from scraped sites unless the user explicitly requests it. For data-protection questions, the operator's own GDPR/CCPA posture should be confirmed with the operator directly.

Plan comparison (captured reference)
PlanPrice /moAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices exclude VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. Figures reflect the captured plan listing and should be re-checked against current pricing before purchase.

Field map: what you get and what it's for
FieldTypical use
Image URLDirect asset reference; deduplication key
Source page URLAttribution; joining to page-level data
Image dimensionsFiltering thumbnails vs full assets
Alt textKeyword and category signals
Visually-similar referencesRelated-asset discovery

Frequently asked questions

Do I need an account to scrape image search results?

You don't need an account on the image search engine itself. You do need an API key from the scraping service — sign-up includes free trial credits and no card is required to start. After that, you send the URL and the service handles rendering and proxies.

Is scraping image search results legal?

Public-facing pages can usually be collected, but the target site's terms of service should be reviewed before you deploy, and post-login content should be avoided. Legal advice specific to your jurisdiction and use case is outside the scope of this page.

What's the rate limit for scraping image search results?

The API enforces concurrency limits per plan rather than per-target rate limits. If the image search engine itself throttles aggressive patterns, space out requests or spread them across multiple sessions.

How do I get structured JSON from image search results?

Pass extract_rules with CSS selectors mapped to your field names, or use ai_extract_rules with a natural-language spec. Either way the response comes back as parsed JSON.

Which programming languages can I use to scrape image search results?

Any language that can make an HTTP request. SDKs exist for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works as well — pick whatever your stack already uses.

How much does it cost to scrape image search results?

Free trial credits are available at sign-up with no card required. Paid plans start at $19/month. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium proxy with JS, and 75 for stealth proxy. See the plan comparison table above for full tier details.