# Amazon product API: any product's detail by ASIN

Give your agent an ASIN and get the listing back as data: title, current price, images, specifications and the review summary. 3 providers do this through one treg.to key, from $0.0015 a product, with no Amazon programme to be approved for first. That last part is most of the reason this job has a price at all.

## What's the best way to ask ChatGPT?

Setup line (paste into any agent): `set up treg — https://treg.to/llms.txt`

Then ask: "Using treg, get the Amazon product detail for ASIN B08N5WRWNW on amazon.com. Show me the price first, then give me the title, current price, rating and review count."

- **Give it the ASIN and the marketplace** One ASIN is a different listing and a different price on each Amazon domain. Name the one you mean.
- **Ask for the price first** treg.to returns the cost before the call, so the agent can say what it will spend.
- **Name the fields you want back** A product payload is large. Saying which fields matter keeps the answer short and the context small.
- **Say what to do on a miss** Dead and region locked ASINs are normal in any list. Tell it to skip and report rather than retry.

## Why go through treg.to

- **One key, not 9 accounts** treg.to holds the provider keys. Neither you nor the agent sees them.
- **Price before the call** The provider's own rate, $0.000 markup, from a prepaid balance.
- **No subscription, no seats** Charged per call. $1.00 free per new team, no card to start.
- **Your own keys are free** Already pay Hunter? Register it and those calls are never metered.
- **Switch by changing a word** Another provider is a different word in the prompt, not a new integration.
- **Nothing to integrate** No SDK, no OAuth dance per vendor, no seats.

## Behind the scenes: what ChatGPT sees before it calls

treg.to does not choose for you. It hands ChatGPT this comparison and it picks, or you tell it how.

### Which Amazon product API is cheapest?

- Cheapest per result: Bright Data at $0.0015 (`brightdata.x.amazon-products`)
- Cheapest per found: Just One API at $0.0148 (`justoneapi.x.amazon-get-product-detail-v1`)

Those units are not interchangeable: one call can return many results, so compare on the unit you will actually be billed in.

### Which one is the most reliable?

- Just One API: 100% over 17 calls, 5.6s median
- SerpApi: 100% over 157 calls, 8.3s median

Measured on treg.to traffic; not a controlled benchmark.

### How do the providers compare?

| Provider | Price | Accepts | Verified |
|---|---|---|---|
| Bright Data | $0.0015 per result | dataset_id, format, input | 2026-07-30 |
| Just One API | $0.0148 per found | asin, country | 2026-07-28 |
| SerpApi | $0.015 per found | engine, asin, amazon_domain | 2026-07-28 |

Endpoints:

- `brightdata.x.amazon-products`: treg call brightdata.x.amazon-products --query dataset_id=gd_l7q7dkf244hwjntr0 --query format=json --data '[{"url":"https://www.amazon.com/dp/B08N5WRWNW"}]'
- `justoneapi.x.amazon-get-product-detail-v1`: treg call justoneapi.x.amazon-get-product-detail-v1 --query asin=B08N5WRWNW --query country=US
- `serpapi.x.amazon-product`: treg call serpapi.x.amazon-product --query engine=amazon_product --query asin=B072MQ5BRX --query amazon_domain=amazon.com

## What people actually struggle with

From roughly 28 on-topic Reddit posts in August 2026, of which 16 were vendor written and excluded: four in one vendor's own subreddit, two of those word for word identical, plus one account running the same buying question through three scraping subreddits. The X half of the research held nothing organic on this job at all. What survived says something different from the marketing, so this page is built on it.

**The official API is gated behind a business you may not be in**

> "I applied for the official Amazon Product Advertising API (PA-API), got my keys, but for some reason, they never actually granted me functional access." (r/developersIndia, 103 points: https://www.reddit.com/r/developersIndia/comments/1q4i0l8/amazon_denied_my_api_access_so_i_built_my_own/)

What this page can do about it: The highest scoring organic post in the research, and the theme the marketing around this job never mentions, because it is easier to sell you a fix for blocking. Amazon's product API belongs to its affiliate programme, so it is granted to people earning it commission, not to people who want product data. Every row on this page sidesteps that by inverting the relationship: you are paying for data rather than being paid for referrals.

**The deadlock: no API without sales, no sales without the API**

> "How do you get approved for Amazon Affiliate marketing if you cannot use the product advertising API without being approved first?" (r/Affiliatemarketing, 2 points: https://www.reddit.com/r/Affiliatemarketing/comments/1alp1an/how_do_you_get_approved_for_amazon_affiliate/)

What this page can do about it: A fair question with an uncomfortable answer, and worth spelling out because the same poster goes on to ask whether to host Amazon's images anyway. Buying the data from a third party breaks the deadlock and does not touch the licence: these rows return image URLs, they do not grant you Amazon's rights to those images. If your plan needs the images, the affiliate programme is still the route, and this page is not a way around it.

**An agent asked to read a listing will invent one instead**

> "You cannot use Chatgpt to search Amazon products - it won't even open links" (r/OpenAI, 50 points: https://www.reddit.com/r/OpenAI/comments/1ph2nul/you_cannot_use_chatgpt_to_search_amazon_products/)

What this page can do about it: The thread underneath is the interesting part: the model did not fail loudly, it substituted a price from elsewhere and insisted it had read the listing. That is the failure mode that matters for agents, because it looks like an answer. A priced call against a named ASIN turns it into a fetch with a cost and a result, which is checkable in a way a confident paragraph is not.

**A hand rolled scraper meets the CAPTCHA within a few dozen pages**

> "I tried using random user agents, time.sleep() to avoid that darned captcha page." (r/webscraping, 4 points: https://www.reddit.com/r/webscraping/comments/yn1cvl/bot_detection_with_python_requests/)

What this page can do about it: This is the second act of nearly every story in the research: the official route is shut, so people write the script, and the script dies somewhere in the first hundred pages. What changes here is who owns the repair. What does not change is that every provider in this space fails some proportion of requests, so the honest question is not who never fails but who tells you when they did, and what that failure costs you.

**The proxy fixes the blocking and hands you the latency**

> "Requests without the proxy had an average response time of 1.5 seconds. However, with the proxy, the response time increased to around 6-10 seconds." (r/scrapy, 1 point: https://www.reddit.com/r/scrapy/comments/187goqh/requests_through_the_rotating_residential_proxy/)

What this page can do about it: Worth quoting precisely because it is not the complaint the vendor content wants you to have. In the organic posts the grievance about proxies is speed and upkeep, not price; the same poster calls his provider the cheapest he found. So compare on the whole cost of the do it yourself path, the maintenance and the seconds, rather than on a monthly proxy bill, and be sceptical of any page here or elsewhere that opens on how expensive proxies are.


## What actually differs

- The three rows do not take the same key, which is work before it is price. Bright Data takes a product URL and returns records from its Amazon dataset. JustOneAPI takes the ASIN with a country code. SerpApi takes the ASIN with an Amazon domain. If what you hold is a list of bare ASINs, two of these are a direct call and the third needs a URL built first.
- There is no single true price for an ASIN, and that is not a gap in this comparison. What a product page shows depends on the marketplace, the delivery address, whether the viewer has Prime and which seller holds the buy box that second, so no provider can be more accurate in the abstract. The checkable difference is which of them lets you pin the context: a country code here, an Amazon domain there, and on the URL based row whatever marketplace the URL points at.
- Every row bills only what succeeds, which is what makes a long unverified list safe to hand an agent. Two are priced per successful call and the third per record actually delivered, so an ASIN that is dead, region locked or withdrawn costs nothing. What you can still run up is your own retry loop, so tell the agent to skip and report rather than to try harder.

## What is an Amazon product API?

It returns one Amazon listing as structured data rather than as a page: the title, the price showing at the moment of the call, images, the specification table, the rating and the review count. It is not Amazon's own API and it is not a feed. Each call reads a public product page as an anonymous visitor would see it, which is what makes it available without an Associates account and also what sets the edges of what it can ever return.

## Questions

**How much does one product lookup cost?** A fraction of a cent to about a cent and a half depending on the row, at the provider's own rate with $0.000 added by treg.to. The live figures are in the comparison above, and all three bill only when the lookup works.

**Why not use Amazon's own API?** Because neither of Amazon's APIs is a general read any product API. The Product Advertising API belongs to the affiliate programme and is granted to accounts earning qualifying commission, which is why people report keys that never became working access. The Selling Partner API is for managing your own selling account. If you are in neither programme, there is no official door.

**Do these give me the right to use Amazon's product images?** No, and it is worth being blunt because the research is full of people asking. A data API returns image URLs; it does not hand you Amazon's licence to host or republish them. Rights to product imagery come from the affiliate programme or from the brand, and no amount of paying for data changes that.

**Can I look up thousands of ASINs?** Yes, and the cost is linear because it is one call per ASIN with no batch endpoint. Your agent runs the list; treg.to prices each call and shows the running total, and since all three rows bill only on success, the dead entries in a scraped list do not cost you anything.

HTML version: https://treg.to/use-cases/e-commerce/amazon-product-detail-by-asin