Compare · Bright Data / Oxylabs / Decodo / ScraperAPI / Zyte / Apify

Generic scrapers and proxies, or an Amazon data API?

A successful request does not mean complete search data. Many scrapers miss Sponsored ads. Pangolinfo returns the search page a real shopper sees for a given marketplace and ZIP code, with organic and Sponsored results kept separate.

Real shopper search page Marketplace + ZIP context Organic and Sponsored kept separate API · MCP · Skill

Generic scrapers vs an Amazon data API in 3 minutes

Jump to chapter
Note: The video shows one real API call. Timing and result counts vary by keyword, ZIP code and time.

“Generic scraping” actually means three different routes

Traditional scrapers and proxies

Usually deliver raw HTML. Parsing, ZIP context and Sponsored detection stay on you. Best for multi-site projects with an in-house scraping team.

Platform Amazon data products

Bright Data, Oxylabs, Decodo and others offer structured product and search data; some support MCP. ZIP, Sponsored and review coverage vary by vendor.

Three easy-to-miss costs when scraping Amazon the traditional way

Data completeness cost

A 200 response can still omit Sponsored ads. In Pangolinfo ongoing monitoring and internal testing, traditional generic scrapers typically capture about 30%–60% of Sponsored placements; recheck with the same keyword, marketplace and ZIP.

Parser maintenance cost

With HTML only, you extract and validate fields yourself. When Amazon pages change, you also debug parsers and missing data—ongoing engineering time.

Traffic and retry cost

Public residential proxy list prices often run about $2–8 per GB. Large pages, CAPTCHAs and retries burn bandwidth; failed requests can still consume budget.

Rebuild the real search page, then deliver structured data

STEP ①

Pass an ASIN, keyword, category or seller

STEP ②

Set marketplace and ZIP code

STEP ③

Collect in a real shopper context, then parse and validate Amazon fields

STEP ④

Return JSON, HTML or Markdown

Coverage: Product detail, keyword search (organic and Sponsored), category listings, seller listings, Best Sellers, New Releases. Review data comes from a dedicated Amazon Review API; the Amazon Alexa API provides natural-language shopping Q&A, AI-generated answers and related product recommendations—not Alexa website traffic rankings.

The request succeeded. Are the ads still there?

Missing Sponsored slots are often an environment problem, not a parsing bug. The most direct vendor check is a side-by-side run with your own keywords.

1 Pick the same keyword set
2 Lock the same marketplace and ZIP
3 Call each vendor in the same window and compare Sponsored count and position per page

Reference: In Pangolinfo ongoing monitoring and internal testing, traditional generic scrapers typically capture about 30%–60%; treat your own results as ground truth.
Prefer not to write code first? Copy the cURL sample from the docs, or call Amazon Data MCP from Claude Code, Cursor or another MCP client.

Start testing on the free plan
# 1. Replace YOUR_API_TOKEN & test side-by-side
# Docs: https://docs.pangolinfo.com/en-api-reference/amazonApi/amazonScrapeAPI

curl -X POST "https://api.pangolinfo.com/v1/amazon/search" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "coffee maker",
    "marketplace": "US",
    "zip_code": "10041"
  }'

Capability comparison

Dimension Traditional scrapers / proxy gateways Leading-platform Amazon products Pangolinfo
Output Usually HTML; you parse it Structured JSON and more JSON, HTML, Markdown
ZIP code Build it yourself Supported by some vendors Marketplace + ZIP
Sponsored ads Often missing when the environment looks off A field on the schema ≠ reliable capture; test it Rebuilds the real search page and labels ads and positions
Reviews Usually no dedicated full review fields; scrape and parse yourself Some leading platforms have review products; verify fields and scope Dedicated Amazon Review API
Amazon Alexa Usually not offered as dedicated data Many general platforms omit it; verify vendor by vendor Amazon Alexa API: shopping Q&A, AI answers and product recommendations
Category, charts, sellers Build it yourself Varies by vendor Dedicated endpoints for each
MCP Usually none Many offer MCP; tool scope varies 21 tools + Skill, same data as the API
Billing Per GB or per request Per request, result or record Per page
Best fit Multi-site teams with scrapers in-house Multi-site, large scale Amazon-focused workloads

Note: Competitor capabilities are taken from vendor sites and official GitHub; always check each vendor’s latest docs.

How to choose

Route A · Traditional Gateways

Mature scraping team, dozens of sites: pick traditional scrapers or proxy gateways.

Route B · Multi-Site Platforms

Cross-site scale or historical datasets: pick leading platforms such as Bright Data or Oxylabs.

First-Party Seller Account

Orders and inventory from your own seller account: use Amazon’s official SP-API.

Route C · Amazon Market Intelligence

Amazon-focused work that needs full Sponsored and ZIP context, and data ready for systems or AI: choose Pangolinfo.

One real call: ZIP 10041 New York, keyword coffee maker

In the video demo, one call returned 60 results, including 12 labeled Sponsored, in about 3 seconds. Results vary by keyword and time. Try the same keyword, marketplace and ZIP on the tool you already use.

Request Parameters POST
Keyword “coffee maker”
Marketplace Amazon.com (US)
ZIP Code 10041 (New York, NY)
Output Format Structured JSON / HTML / Markdown
Result Summary ~3.0s
60
Total results on page
48
Organic results
12
Sponsored ads

Organic and Sponsored are labeled separately with positions. Exact code and full response shape follow the docs.

Read the docs →

Let AI agents observe. People decide.

AI agents call Pangolinfo over MCP to pull rankings, Sponsored slots and recent negative reviews for a given ZIP in real time. AI observes, groups and flags anomalies; pricing and ad changes still wait for human approval.

01 · Observe

Observe

Pull organic rank, Sponsored ads and recent negative reviews for a marketplace and ZIP via MCP in real time.

02 · Group & Alert

Group and alert

AI groups competitor ad shifts and review pain points, then emits structured anomaly alerts.

03 · Human Approval

Human approval

Price changes, budget moves or bid edits run only after ops or an owner confirms.

Two-vendor cost check: same scenario, 200,000 search pages

Public list-price estimate for 200,000 Amazon keyword search pages per month (November 2026, tax excluded). Billing units differ. JS rendering, ZIP support and data completeness for each vendor should be tested on the same keywords; do not treat record-count or page-count gaps as delivery quality by themselves.

Billed per product record · example

Bright Data

About $12,480
200,000 pages × 48 products per page = 9,600,000 records

Scale plan $499 includes 384,000 records; overage estimated at $1.30/1K records. Billing unit is product records, not search pages. This figure is for record-volume comparison only; JS, fields and Sponsored delivery still need separate verification.

Public list price →
Billed per page

Pangolinfo Expert

$369
Includes 240,000 requests, covering 200K structured search pages

One search page counts as one request, regardless of products on the page. Organic and Sponsored return separately; still verify completeness with your own keywords.

View pricing →

How Bright Data record volume changes the estimate

Same Scale plan and overage rate: 200,000 pages × products per page = product records. Pangolinfo bills per page and does not scale with record count.

Products per pageTotal product recordsBright Data estimateMultiple vs Pangolinfo $369
204.0M recordsAbout $5,200About 14×
489.6M recordsAbout $12,480About 34×
6012.0M recordsAbout $15,600About 42×

Multiples only illustrate the order-of-magnitude gap between per-record and per-page billing; they do not mean every platform already delivers equal data quality.

Shared assumptions: Public list-price estimates, not quotes; tax and promotions excluded. Bright Data example is estimated on product records; Pangolinfo is per page. Multiples show billing-unit differences only, not equal delivered quality. JS rendering, structured fields, ZIP and Sponsored coverage depend on the chosen configuration and same-keyword tests. Product-detail and other workloads need separate math.

Start on the free plan and verify with your own keywords

No card required. Check fields and Sponsored ads with your own ASINs, keywords and ZIP codes, then pick a plan. Paid plans are $19, $99 and $369 per month; contact sales for higher volume. Raw HTML or Markdown uses less quota when that is all you need.

Free
$0
No card · test ads and fields
Starter
$19/mo
Light monitoring and small-scale checks
Pro
$99/mo
Day-to-day business and team collection

FAQ

Yes. Leading platforms already ship structured Amazon data and MCP. Pangolinfo differs by putting Amazon first: it rebuilds the search page a real shopper sees for a marketplace and ZIP; search, product, reviews, category, charts and sellers share one field model across API, MCP and ready-made Skills. Most generic scrapers / proxy gateways and many general platforms do not offer dedicated full review fields or Alexa shopping Q&A, though some leading platforms have review products. Pangolinfo covers reviews via the Amazon Review API and natural-language shopping Q&A, AI answers and related recommendations via the Amazon Alexa API; Alexa here is not website traffic rankings.
Based on Pangolinfo ongoing monitoring and internal testing, Amazon may withhold ads when the collection environment looks off, while organic results still return and the request still succeeds. In our testing, traditional generic scrapers typically capture about 30%–60%; verify with the same keywords, marketplace and ZIP in the same window.
Proxies bill by traffic, and you still pay for retries, CAPTCHAs and parser maintenance. APIs bill per request or per page. Estimate total cost both ways with a week of your real volume.
Yes. Set marketplace and ZIP on the request; docs currently cover 13 Amazon marketplaces.
Structured JSON, raw HTML or Markdown. Choose HTML or Markdown if your own system handles the next step.
Yes. Amazon Data MCP ships 21 tools for Claude Code, Cursor and other MCP clients; you can also install ready-made Skills in agent IDEs and CLI assistants that support them.
SP-API covers orders, inventory and other data from your own seller account. Pangolinfo covers market data on public pages. Teams usually use both.
Yes. Keep other sites on your current platform and move only Amazon collection to Pangolinfo.
Compliance depends on your use case, local law and platform terms—review with counsel before production. Avoiding logged-in content and personal data is common practice.

Scan WhatsApp
to Contact

QR Code
Quick Test