StoreRouter vs. ScraperAPI
A product index vs. a page-fetching API.
ScraperAPI fetches any URL through rotating proxies, handles CAPTCHAs and rendering, and returns the page; for Amazon, Walmart, eBay and Google it also offers structured endpoints that return JSON. StoreRouter answers search and parse from a product index it keeps current across stores, in one schema, so your agent never fetches pages, writes parsers or maps fields.
- /v1/products/search
- /v1/products/parse
- JSON · Markdown
Evidence recorded October 27, 2026 · StoreRouter, formerly Octogen
| Capability | StoreRouter | ScraperAPI |
|---|---|---|
| Model | Product index behind one API | Proxy and rendering API, run per request |
| Discovery | search across covered catalogs | Structured search endpoints for Amazon, Walmart, eBay and Google |
| Product detail | parse a URL into one shared schema | JSON from structured endpoints; other sites return the page unless you train a parser |
| Freshness | Change detection keeps the index current; force a live parse | Live fetch per request; DataPipeline for scheduled jobs |
| Agent access | OAuth MCP, REST, CLI, TypeScript and Python SDKs | Hosted MCP with API key, REST, async API, SDKs |
| Billing | Successful 2xx responses only | 200 and 404 responses; failures after 70 s of retries aren't billed |
| Pricing | $2 / 1k parse · $14 / 1k search | Credit plans from $49 / month for 100,000 credits; 1–75 credits a request |
| Free tier | $5 credit every month | 5,000 credits for 7 days; then 1,000 credits a month |
Fit
Which one fits
Choose StoreRouter when
your agent works with products across many stores: it searches, compares price, stock, materials and fit, and needs every store's products in the same fields without writing parsers, tuning proxy and render settings, or mapping each retailer's output.
Choose ScraperAPI when
you need to fetch pages yourself at a low per-request price: high-volume Amazon, Walmart or Google scraping, sites StoreRouter doesn't cover, or web data beyond product pages, and you'll own parsing, storage and search.
Overview
What each tool does
ScraperAPI is a scraping API: send a URL and it handles proxy rotation, CAPTCHAs and JavaScript rendering, returning the page. Structured data endpoints return JSON for Amazon (search, product, offers, reviews), Walmart, eBay and Google (search, Shopping, news, jobs). For other sites, an AI Parser can turn pages into JSON once you train a custom parser. An async API takes large batches that retry until they succeed, and DataPipeline schedules recurring jobs without code.
StoreRouter keeps a product index across thousands of covered stores and keeps it current by detecting changes and re-crawling them. search queries that index across stores and returns products; parse turns a product URL into the shared schema: variants, per-size stock, price, images, materials and normalized attributes. You call an API; crawling, unblocking and extraction are ours.
This page compares documented approaches. We have not benchmarked ScraperAPI's records, coverage or latency against StoreRouter's.
Architecture
Where the work happens
- Discovery. StoreRouter
searchsends one query across covered catalogs. ScraperAPI's search endpoints query one marketplace at a time; across retailers, its Google Shopping endpoint returns Shopping listings rather than each store's product record. - Parsing. ScraperAPI parses the marketplaces it has structured endpoints for, each with its own fields. Everything else comes back as a page until you train and maintain a parser. StoreRouter writes and verifies an extractor for each covered store and returns every store's products in the same fields, as JSON or Markdown.
- Cost per request. ScraperAPI's credit cost depends on the site and settings: 1 credit for a plain page, 5 for Amazon, Walmart and eBay, 10 with rendering, 25 for Google, and up to 75 with ultra-premium proxies and rendering (credit costs). StoreRouter charges the same price for any covered store.
- Agent workflow. ScraperAPI's hosted MCP server exposes a scrape tool for any URL and structured tools for Google, Amazon, Walmart, eBay and Redfin (ScraperAPI MCP). StoreRouter's MCP exposes the product operations themselves:
search_productsandlookup_product. - Freshness. A ScraperAPI request fetches the live page; DataPipeline repeats jobs on a schedule. StoreRouter answers from an index that tracks changes on covered stores;
parsewithresolutionMode: "on_demand_only"andonDemandCachePolicy: "refresh"forces a live read. - Reach. ScraperAPI reaches nearly any public page through its proxy pool. StoreRouter covers the catalogs in its index;
parsecan resolve other product URLs on demand, with sparser results and no enrichment.
Before you build
Integration notes
- Does StoreRouter work with any retailer URL or only big-name stores?
searchspans covered catalogs; check catalog coverage for the stores your agent needs.parsecan resolve a product URL from an uncovered store on demand, but that result can be sparser, skips enrichment, and doesn't make the store searchable. Coverage expands with request demand. That's the direction, not a guarantee for any given store today.- How does pricing compare?
StoreRouter: $2 per 1,000 parse requests and $14 per 1,000 search requests; only successful 2xx responses are billed (see pricing). ScraperAPI sells monthly credit plans: $49 for 100,000 credits, $149 for 1 million, $299 for 3 million, up to $1,975 for 21.5 million (ScraperAPI pricing). A request costs 1 to 75 credits depending on the site and settings, and 200 and 404 responses are billed.
On a mid-tier plan, an Amazon or Walmart request costs well under StoreRouter's parse price. For a store without a structured endpoint, compare StoreRouter's parse price with a rendered or premium-proxy fetch plus a parser you maintain, and add the mapping, storage and search you'd build on top.
- Can I use this inside an AI agent or LLM workflow?
Yes, both. StoreRouter's MCP server signs in with OAuth, so there's no key to paste, and works with Claude, Cursor and any MCP client; REST, a CLI and TypeScript and Python SDKs cover the rest (MCP docs). ScraperAPI offers a hosted MCP server authenticated with your API key, plus integrations such as LangChain and LlamaIndex.
- Can I use both?
Yes. Use StoreRouter for product search and detail across covered stores, and ScraperAPI for marketplace scraping, other web data and sites outside the index.
Give your agent every store.
Mint a key, send search a real shopping query, and parse the products your agent would recommend.
Documentation reviewed · 2026-10-27
Sources and scope
This page compares documented approaches. We have not run a ScraperAPI benchmark or established better record completeness, accuracy, coverage, freshness or latency.
- ScraperAPI: products, structured endpoints, async API, DataPipeline.
- Pricing: plans, credits, trial.
- Credits and requests: per-site and per-setting credit costs, billed status codes.
- ScraperAPI MCP: hosted endpoint, authentication, tools.
Prices are list rates on the review date, before the 10% annual discount.