StoreRouter vs. Bright Data

A product index vs. a scraper per site.

Q: Does StoreRouter work with any retailer URL or only big-name stores?

search spans covered catalogs; check catalog coverage for the stores your agent needs. parse can 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.

Q: How does pricing compare for high-volume product lookups?

StoreRouter: $2 per 1,000 parse requests and $14 per 1,000 search requests; only successful 2xx responses are billed (see pricing). Bright Data's Web Scraper API: $1.50 per 1,000 records pay-as-you-go, or $499 a month for 384,000 records and $1.30 per 1,000 after that; failed deliveries aren't billed (Bright Data pricing). Per record, Bright Data's list price is lower. Compare what each record contains, and the mapping, storage and search you'd build across sites on top of it.

Bright Data's Web Scraper API runs a pre-built scraper for each retail site and returns that site's record. StoreRouter answers search and parse from a product index it keeps current across stores, in one schema, so your agent never picks, runs or maps a scraper.

Get an API key Check coverage

/v1/products/search
/v1/products/parse
JSON · Markdown

Evidence recorded October 16, 2026 · StoreRouter, formerly Octogen

StoreRouter and Bright Data at a glance
Capability	StoreRouter	Bright Data
Model	Product index behind one API	Pre-built scraper per site, run on request
Discovery	`search` across covered catalogs	Keyword scrapers per retailer; Google Shopping scraper across retailers
Product detail	`parse` a URL into one shared schema	Each site's scraper record; fields vary by site
Freshness	Change detection keeps the index current; force a live `parse`	Live scrape per request, or datasets refreshed on a schedule
Agent access	OAuth MCP, REST, CLI, TypeScript and Python SDKs	Hosted MCP with API token, REST, CLI, Python and Node.js SDKs
Billing	Successful 2xx responses only	Successful records only
Pricing	$2 / 1k parse · $14 / 1k search	$1.50 / 1k records pay-as-you-go; plans from $499 / month
Free tier	$5 credit every month	5,000 records a month

Fit

Which one fits

Choose StoreRouter when

your agent works with products: it searches across stores and compares items on price, stock, materials and fit, and you want every product in one schema without choosing, running or mapping a scraper for each site.

Choose Bright Data when

you need web data beyond product pages, bulk datasets from specific marketplaces, or collection from sites StoreRouter doesn't cover, and you'll map each scraper's output yourself. It also fits teams already running Bright Data's proxy and unblocking infrastructure.

Overview

What each tool does

Bright Data is a web data platform: proxy networks, an unblocking API, a SERP API, and a Web Scraper API with pre-built scrapers for named sites. Its ecommerce scrapers take a product URL or a keyword for one retailer, such as Amazon, Walmart or Target, and return that site's record as JSON or CSV, by API, webhook or cloud-storage delivery. Datasets sells the same kind of records pre-collected or refreshed on a schedule.

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 Bright Data's records, coverage or latency against StoreRouter's.

Architecture

Where the work happens

Discovery. StoreRouter search sends one query across covered catalogs. Bright Data's keyword scrapers search one retailer at a time; for results across retailers, it points to its Google Shopping scraper, which returns Shopping listings rather than each store's product record.
Schema. Each Bright Data scraper defines its own fields: its Amazon scraper lists list price and currency, its Walmart scraper final price and GTIN. Combining stores means mapping each one. StoreRouter returns every store's products in the same fields, as JSON or Markdown, with normalized attributes and enrichment on indexed products.
Agent workflow. Bright Data's MCP server exposes scrapers as tools: find a scraper, read its details, run it, check progress, fetch results (Bright Data MCP). StoreRouter's MCP exposes the product operations themselves: search_products and lookup_product.
Freshness. A Bright Data scraper fetches the live page when you run it; pre-collected datasets were gathered days to months earlier unless you order a refresh. StoreRouter answers from an index that tracks changes on covered stores; parse with resolutionMode: "on_demand_only" and onDemandCachePolicy: "refresh" forces a live read.
Reach. Bright Data's scrapers and proxy network extend well beyond ecommerce. StoreRouter covers the catalogs in its index; parse can 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?

search spans covered catalogs; check catalog coverage for the stores your agent needs. parse can 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 for high-volume product lookups?

StoreRouter: $2 per 1,000 parse requests and $14 per 1,000 search requests; only successful 2xx responses are billed (see pricing). Bright Data's Web Scraper API: $1.50 per 1,000 records pay-as-you-go, or $499 a month for 384,000 records and $1.30 per 1,000 after that; failed deliveries aren't billed (Bright Data pricing).

Per record, Bright Data's list price is lower. Compare what each record contains, and the mapping, storage and search you'd build across sites on top of it.

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). Bright Data offers a hosted MCP server authenticated with an API token, plus Python and Node.js SDKs and a CLI.

Do free and purchased credits expire?

StoreRouter gives every organization $5 of credit each month; purchased credit never expires. Bright Data's free tier is 5,000 records a month, and unused free usage doesn't roll over.

Can I use both?

Yes. Use StoreRouter for product search and detail across covered stores, and Bright Data for other web data, marketplace datasets 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.

Get an API key Check coverage

Documentation reviewed · 2026-10-16

Sources and scope

This page compares documented approaches. We have not run a Bright Data benchmark or established better record completeness, accuracy, coverage, freshness or latency.

Ecommerce Scraper API: per-site scrapers, output fields, formats, delivery, free tier.
Web Scraper API pricing: pay-as-you-go and Scale rates, success-only billing.
Ecommerce datasets: pre-collected and scheduled records.
Bright Data MCP: hosted endpoint, token authentication, scraper tools.

Bright Data describes its free tier as both 5,000 records and 5,000 credits a month shared with its Unlocker and SERP APIs; we quote records. Prices are list rates on the review date, before promotions.

Endpoints

Surfaces

Discover More