"Does an Amazon API cost money?" is really three questions: what you pay for access, what you pay for the data, and what your own time costs. This post answers the second one with numbers and gives a way to estimate the third. It does not quote the first.
Amazon's own Selling Partner API is governed by Amazon. Its access terms, including any fees, are Amazon's to set and can change, so read them in Amazon's developer documentation instead of in a blog post. What it covers is your own store's data; that split is explained in choosing an Amazon data API.
What this site charges
Prices are taken from the pricing page as of 29 September 2026, and are in US dollars.
| Pack | Calls | Price | Per call | Cheaper per call than the pack above |
|---|---|---|---|---|
| Trial | 50 | $1.99 | $0.0398 | — |
| Starter | 600 | $6.99 | $0.0117 | 71% |
| Growth | 1,500 | $13.99 | $0.0093 | 20% |
| Team | 8,000 | $69.99 | $0.0087 | 6% |
The rules that go with it:
- One-time purchases. There is no subscription and no per-seat fee. You top up when the balance runs low.
- Credits are valid for 60 days. Calls you have not used by then are gone.
- One balance for every public endpoint. A pack does not unlock more or fewer endpoints.
- One call per successful billable request. All 46 endpoints use one call today; the pricing page says an endpoint will state it if that changes.
- Failed requests are not charged if they fail before a billable result is returned, and the final status and billable units are in your usage records.
- There is no free tier. Creating an API key costs nothing, but a call uses credit. What you can do without paying is covered in which Amazon data you can get for free.
The price curve flattens quickly
The big step is from Trial to Starter, where the per-call price falls by 71%. Growth is another 20% cheaper. Team is only 6% cheaper per call than Growth.
That changes how to read the pack list. The Team pack is not a discount you grow into; it makes sense only when you would otherwise buy Growth five times. Four Growth packs are 6,000 calls for $55.96, and five are 7,500 for $69.95, about the price of a Team pack that gives 8,000. Below roughly 6,000 calls in 60 days, Growth is the better buy.
Turn a workflow into a call count
Do not estimate from pack size. Count the calls your workflow makes, over the 60 days the credits last.
| Workflow | Calls | Where the number comes from |
|---|---|---|
| Monitor 20 competitor ASINs daily | 20 × 60 = 1,200 | One details call per ASIN per day. Fits one Growth pack. |
| Screen 1,000 category nodes once | 5 | Market Research returns up to 200 rows a page. |
| Read every search term matching one query | 121 | The documented ABA example matches 4,835 terms, and a page holds at most 40 rows. |
The last row is the one to notice. Reading everything that matches a broad query costs 121 calls, about a fifth of a Starter pack. Filter first: add a rank ceiling or a growth floor, as in reading ABA search terms, and the same question can take a handful of calls. The market screen in building a niche finder works the same way.
Where calls get wasted
Pulling data more often than it changes. The ABA weekly report is keyed on a Saturday. Fetching it every day repeats the same answer six times out of seven.
Repeating the same request. A product's title and category rarely change; its price and rank do. Store the first and refresh the second. The trade-off is set out in five decisions to settle before you integrate.
Retrying without looking. A 429 means the account's per-minute limit was reached, and the limit is per account, so extra API keys do not raise it. Honour Retry-After and back off, as described in errors and rate limits. A 402 means the balance is empty; a retry will not fix it.
Buying for volume you will not use. Credits expire after 60 days. A Team pack used at 10% costs more per call than a Starter pack used in full.
The cost that is not on the pricing page
Calls are the visible cost. The other one is the time to make them useful: writing and testing the integration, handling errors and limits, storing results, and watching the balance. It differs by team and this post gives no figure for it.
Two things shrink it. The remote MCP server lets an AI agent make the calls with no code, and the getting-started guide walks through a first request. The alternative, building the collection yourself, has its own costs; four hidden costs of building an Amazon scraper lists them.
Estimate your own bill
- Write down the workflows you will run and how often.
- For each, count calls per run: pages, ASINs, terms.
- Multiply by runs in 60 days, and add a margin for retries.
- Pick the smallest pack that covers the total. Top up later if you need more.
If the total is under 50, the Trial Pack is enough to prove the method. Above 8,000 in 60 days, contact support for a higher-volume package.
FAQ
Is there a free trial? No. There is no free call allowance. The smallest pack is 50 calls for $1.99.
Do unused calls roll over? No. Credits are valid for 60 days from purchase.
Do different endpoints cost different amounts? Not today. Every one of the 46 endpoints uses one call per successful request. The pricing page notes that an endpoint's documentation will say so if that changes.
Is it cheaper than a subscription tool? This post does not compare against other providers' prices. Compare on your own call count and on what the data has to be able to do.
Are prices in US dollars? Yes. Pack prices are in US dollars. Where a page shows another currency as a reference, the amount actually paid is the dollar price.