Mine Amazon reviews for product flaws and feature requests
Read Amazon reviews by ASIN as JSON with stars, title, text, date and verified purchase, to find defects and feature requests to build into your product.
Product teams and sellers know that the reviews of competing products list the flaws buyers care about, in the buyers' words. Reading a few hundred by hand does not give you a ranked list. Lovely Router reads them for you. Send an ASIN, get one JSON object per review, pay per review from a prepaid balance. Call it from a script, a product review or an AI agent with one API key.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Mine Amazon reviews for product flaws and feature requests. Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <the inputs (links, keywords or accounts) and how many results you need>How it works
Pick the products
Choose your own ASIN and the best-selling competitors, and the Amazon site they sell on.
Run the tool with a cap
Send them to
POST /v1/tools/amazon-reviews/runwithmaxPagesfor each ASIN andmax_resultson the request. The run holds its maximum cost from your balance and returns the reviews as JSON.Group and rank themes
Filter to low-star reviews, group them by topic with a model, and rank the complaints by how often they occur.
Pull reviews for an ASIN with one request
List Amazon reviews takes a list in input, one entry per ASIN. Each entry has asin, domainCode, sortBy and maxPages. Reviews come in pages of 10, and one run returns up to 100:
curl https://lovelyrouter.com/v1/tools/amazon-reviews/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{
"input": {
"input": [
{
"asin": "B08C1W5N87",
"domainCode": "com",
"sortBy": "recent",
"maxPages": 1
}
]
},
"max_results": 10
}'maxPages sets how many pages of 10 reviews to read for each ASIN. A run still going after 60 seconds returns 202; Run a tool shows how to poll.
What each review holds
| Field group | What you get |
|---|---|
| Rating | Stars |
| Content | Review title and text |
| When | Date |
| Trust | Whether it is a verified purchase |
A review with low stars and a verified purchase is the strongest signal; filter on both before you count themes.
Recipes
Pull the most recent reviews of three rival products, keep the ones with one or two stars, and ask a model to group them by cause with a count for each.
Read the five-star reviews of the leader and extract the features buyers name; those are what your listing should lead with.
Sort by recent, run your own ASIN each week and watch for a new theme in one-star reviews.
Split reviews by verified purchase and see whether the complaints differ.
Export the top five defect themes with example quotes and attach them to your next supplier call.
Prefer plain words? Connect the MCP server and tell Claude Code or Cursor: "Read 100 recent reviews of ASIN B08C1W5N87 on amazon.com, keep the ones with 3 stars or fewer, and give me the five most common complaints with two quotes each. Set max_results to 100."
Pair it with product data and other review sources
Amazon reviews are one voice. These add the product page and other places buyers talk:
Customer reviews for an Amazon ASIN: stars, title, text, date, verified purchase. Reviews come in pages of 10 (maxPages in the input).
Full Amazon product page by ASIN: price, rating, features, images, seller, rank.
Amazon Best Sellers for a category: rank, title, price, rating, ASIN.
Trustpilot reviews of a company by domain: stars, text, date, reply.
Reddit posts for a query or subreddit: title, body, score, comments count, author, date.
amazon-productreads the product page behind the reviews: features, price, seller and rank.amazon-bestsellersgives you the competitor ASINs to mine.trustpilot-reviewsreads company reviews on Trustpilot.reddit-searchfinds longer, unprompted discussions of the same product type.
For ongoing monitoring across review sites, see review monitoring.
What you pay
You pay per review: starting a run holds its maximum cost, the per-call fee plus the per-review fee times max_results, and the run settles to what it returned. The rest of the hold goes back to your balance. A run that fails or times out pays only for the reviews it delivered, and a run refused at the start costs nothing.
Reading 300 reviews across three products is billed as 300 reviews. There is no subscription and no monthly minimum: top up from $5, and one balance pays for tools and models. The card above shows today's price; pricing lists every tool.
Frequently asked questions
How many reviews do I get per page?+
Reviews come in pages of 10, and maxPages sets how many pages are read for each ASIN.
Can I get the most recent reviews first?+
Yes. The example input uses sortBy set to recent.
Can I read reviews from other Amazon sites?+
The input has a domainCode field; the example uses com. Set it to the site of the ASIN you want.
How many reviews can one run return?+
From 10 up to 100 per run.
Can I tell verified purchases apart?+
Yes. Each review says whether it is a verified purchase.
Do I need a subscription?+
No. You add credit to a prepaid balance and each run draws it down. Failed runs pay only for the results they delivered, and nothing renews automatically.
Watching reviews over time? See review monitoring, Amazon listing audits and the tool catalog.