StoreRouter vs. Oxylabs
A product index vs. a scraper per target.
Oxylabs' Web Scraper API fetches pages through its proxy network and, for targets with a dedicated parser, returns that site's fields as JSON; other URLs come back as HTML for you to parse. StoreRouter answers search and parse from a product index it keeps current across stores, in one schema, so your agent never picks a target, writes a parser or maps fields.
- /v1/products/search
- /v1/products/parse
- JSON · Markdown
Evidence recorded October 27, 2026 · StoreRouter, formerly Octogen
| Capability | StoreRouter | Oxylabs |
|---|---|---|
| Model | Product index behind one API | Scraper API run per request, with per-target parsers |
| Discovery | search across covered catalogs | Search targets per retailer; Google Shopping across retailers |
| Product detail | parse a URL into one shared schema | Each target's parsed fields; HTML for other sites unless you add a parser |
| Freshness | Change detection keeps the index current; force a live parse | Live scrape per request; scheduler for recurring jobs |
| Agent access | OAuth MCP, REST, CLI, TypeScript and Python SDKs | Hosted MCP with API token or username and password, REST, Python SDK |
| Billing | Successful 2xx responses only | 2xx and 4xx results; its own 5xx, 6xx and 429s are free |
| Pricing | $2 / 1k parse · $14 / 1k search | From $0.50 / 1k results (Amazon) to $1.50 / 1k (custom JS); plans from $30 / month |
| Free tier | $5 credit every month | $5 welcome credit, once |
Fit
Which one fits
Choose StoreRouter when
your agent works with products across many stores: it searches and compares items on price, stock, materials and fit, and you want every store's products in the same fields without writing parsers, choosing render modes or mapping each retailer's output.
Choose Oxylabs when
you need raw web access at the lowest per-request price: high-volume Amazon or Google scraping, results geo-targeted down to city or ZIP code, sites StoreRouter doesn't cover, or web data beyond product pages, and you'll own parsing, storage and search. It also fits teams already buying Oxylabs proxies.
Overview
What each tool does
Oxylabs is a proxy and web data provider: residential, datacenter and mobile proxies, a Web Scraper API, AI Studio for prompt-driven scraping, and Datasets. The Web Scraper API has dedicated targets for large marketplaces such as Amazon, Walmart, Target, Best Buy, eBay, Etsy and Wayfair, several with parsed JSON: its Amazon product target lists 129 data points, its Walmart product target 59. A universal target fetches any URL and returns HTML; you can attach your own XPath or CSS parser, or pay for AI parsing. Results come back in real time or land in cloud storage, and a scheduler runs recurring jobs.
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 Oxylabs' records, coverage or latency against StoreRouter's.
Architecture
Where the work happens
- Discovery. StoreRouter
searchsends one query across covered catalogs. Oxylabs' search targets query one retailer at a time; across retailers, its Google Shopping target returns Shopping listings rather than each store's product record. - Parsing. Oxylabs parses the sites it has a dedicated target for, each with its own fields. Everything else is HTML until you write and maintain a parser, or add AI parsing per page. StoreRouter writes and verifies an extractor for each covered store and returns every store's products in the same fields, as JSON or Markdown.
- Agent workflow. Oxylabs' MCP server exposes scraping tools such as
universal_scraper,amazon_product_scraperandgoogle_search_scraper, plus AI Studio tools such asai_scraperandai_crawler(Oxylabs MCP). StoreRouter's MCP exposes the product operations themselves:search_productsandlookup_product. - Freshness. An Oxylabs request scrapes the live page; the scheduler repeats jobs at the interval you set. StoreRouter answers from an index that tracks changes on covered stores;
parsewithresolutionMode: "on_demand_only"andonDemandCachePolicy: "refresh"forces a live read. - Reach. Oxylabs reaches nearly any public page, with geo-targeting across 195 countries. 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). Oxylabs' Web Scraper API is sold as monthly plans from $30, with per-result rates by target: Amazon from $0.50 per 1,000, other targets from $1.00, and JavaScript-rendered custom domains from $1.50; AI parsing is $3.00 per 1,000 pages (Oxylabs pricing). Oxylabs bills 2xx and 4xx results; its own 5xx and 6xx errors and 429s are free.
For a dedicated target like Amazon, Oxylabs' list price is lower per request. For a store without one, compare StoreRouter's parse price with a rendered scrape plus a parser you maintain or AI parsing, 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). Oxylabs offers a hosted MCP server authenticated with an API token or username and password, plus integrations with frameworks such as LangChain, CrewAI and the OpenAI Agents SDK.
- Do free and purchased credits expire?
StoreRouter gives every organization $5 of credit each month; purchased credit never expires. Oxylabs gives new accounts $5 of welcome credit toward any product; its self-service purchases are non-refundable.
- Can I use both?
Yes. Use StoreRouter for product search and detail across covered stores, and Oxylabs for proxies, geo-targeted 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 an Oxylabs benchmark or established better record completeness, accuracy, coverage, freshness or latency.
- E-Commerce Scraper API: targets, parsers, output formats, scheduler, delivery.
- Web Scraper API pricing: plans, per-target rates, AI parsing.
- Billing information: which results are billable.
- Oxylabs MCP: hosted endpoint, authentication, tools.
Prices are list rates on the review date, before promotions and VAT.