What is an Amazon scraper?
An Amazon scraper is a tool or workflow that collects selected information from Amazon pages into a structured result, such as a CSV of product titles, displayed prices, ratings, and availability. With ego(lite), the scraper is your own AI agent working in a real browser: it opens each public product, search, or Best Sellers page in a visible Space and records the fields the page displays, together with the source URL, checked-at time, and access status.
How does Amazon scraping work with ego(lite)?
Give Codex or Claude Code the prompt on this page plus your product or search URLs and the fields you need. The agent opens each source in a separate ego(lite) Space, copies the values the page visibly displays, and returns CSV or Markdown rows with a status for every source. If Amazon asks for sign-in, shows a robot check, or needs another human decision, it stops in that Space and lets you review or take over.
What data can an Amazon product scraper collect?
From a public product page, the agent records the fields the page displays: the title, ASIN when shown, displayed price, list price or discount label, star rating, ratings count, availability or delivery text, brand, and the Ships from / Sold by line. Values are copied exactly as Amazon shows them, and anything the page does not display stays marked as not displayed instead of being guessed.
Can it scrape Amazon search results and Best Sellers pages?
Yes. Point the agent at a search results URL or a Best Sellers list and it first records the visible results with their titles, URLs, and displayed prices, noting Sponsored placements the page labels. It can then open up to a number you set of those products, one at a time in separate Spaces, and record the full product fields for each.
Is this an Amazon scraping API?
No. ego(lite) is an agent-driven browser workflow, not a hosted API endpoint. There are no API keys, credits, or JSON quotas. If you need thousands of rows per day inside a server-side pipeline, Amazon's official Selling Partner API, the Product Advertising API, or a dedicated service is the better fit. This workflow is for bounded lists where you want the run observable and every row source-linked.
Is scraping Amazon allowed?
Amazon's Conditions of Use prohibit data mining, robots, and similar automated collection without consent, and rules differ by jurisdiction and use, so review them before you run any collection. This workflow is deliberately conservative: it reads only public values your own browser session already displays, respects sign-in walls, robot checks, and rate limits instead of bypassing them, and keeps a source trail for review. None of this page is legal advice.
Can I use it to track Amazon prices over time?
You can rerun the same product list whenever you want a fresh check. Because every row keeps its displayed price and checked-at time, comparing two runs shows exactly what changed between checks. What the workflow does not do is run continuously in the cloud or reconstruct price history the page never displayed; each run records only what the session saw at that moment.
Can it scrape Amazon reviews?
Only what the current session visibly displays, which has become very little. Since May 2026, Amazon returns full review pages only to signed-in sessions, and signed-out product pages no longer include review text. The agent records the star rating and ratings count the page shows and marks review content as unavailable instead of working around the restriction. For review data at scale, there is no honest public route.
Why is a scraped Amazon price different from what I see?
Amazon prices and availability depend on the marketplace domain, the delivery location, current offers, and sometimes the session viewing the page. That is why every row in this workflow records the marketplace, the displayed delivery location, and the checked-at time next to the price. When two people see different numbers, the report shows which page state produced each one.
Is ego(lite) a free Amazon scraper?
ego(lite) is free to download for Mac, and the agent doing the work is your own Codex or Claude Code. There are no scraping credits, per-row charges, or sign-up walls in this workflow. What it can record is limited by what your browser session can see, not by a meter.
How is this different from Amazon scraper APIs and no-code crawlers?
Scraper APIs and no-code crawlers run in someone else's cloud, meter output by credits, and sell proxy rotation and CAPTCHA handling as the answer to Amazon's defenses. ego(lite) runs in a visible browser on your Mac with the agent you already use: the scope stays bounded by your input list, nothing is bypassed, and every row keeps its source URL, marketplace context, checked-at time, and access status so results stay reviewable.
What happens when Amazon shows a CAPTCHA or robot check?
The agent stops in that Space and records the visible restriction instead of solving or bypassing it. You can inspect the browser state, complete the check yourself if appropriate, or end the run. The report keeps the source, time, and blocked status so a limited result is never mistaken for a complete one.
Do I need a proxy to scrape Amazon?
Not for this workflow, and ego(lite) does not configure rotating residential or datacenter proxies. Proxy choice cannot make an unauthorized collection acceptable or guarantee that Amazon will not challenge a run. Keep the list small, use the marketplace and delivery context you are authorized to access, respect the site's rules, and switch to an official or licensed feed when you need reliable server-side volume.
Can an Amazon scraper collect every review with pagination?
Only if the current authorized session visibly exposes those review pages, and the signed-out product page may not. The agent can follow a bounded set of visible review-page links and record the text it is allowed to see, but it never works around sign-in or access restrictions. For the common signed-out case it records the displayed star rating and ratings count and marks review text as unavailable rather than claiming a complete review export.
How do I detect a silent Amazon scraping failure?
Require a status and evidence row for every source, not just a process exit code. This workflow records the URL, checked-at time, marketplace, displayed fields, and an access note; it marks a robot check, empty result list, removed listing, or not-displayed field explicitly. Before using the CSV, compare row counts and required-field coverage with the input list and open a sample of source links so a layout change or stale page cannot look like a successful empty export.
Is a managed Amazon scraping API worth it versus building in-house?
Choose a managed API or Amazon's official APIs when you need scheduled, high-volume, server-side data and are prepared to meet their credentials, cost, and policy requirements. Build in-house when you need full control over code and can maintain selectors, retries, observability, and compliance yourself. ego(lite) fits the smaller middle: a focused, authorized list in a visible local browser where reviewing the live page and its evidence matters more than unattended scale.
Can I export Amazon scraper results to Google Sheets?
Yes, by exporting the CSV from the report and importing it into Google Sheets; the sheet retains the source URL, displayed value, checked-at time, and status columns for review. ego(lite) does not silently publish to a third-party spreadsheet or keep a background sync running. If you automate an import, add your own permissioned workflow and preserve the original CSV so the browser evidence remains auditable.