A Better, Cheaper Keepa API Alternative
Get historical Amazon product data since 2023 at a lower cost. Access the data when you need it—without waiting for tokens to refill.
Go beyond history with ranked and grouped product search, keyword suggestions, brand and seller intelligence, bestseller scraping, Today’s Deals, Walmart data, and category taxonomy.
Search your own products. See what the API returns.
The demo doubles as a coverage check: enter one of your ASINs, a barcode, a keyword or an Amazon product link. A product we hold shows its full record and history; one we don’t hold yet is fetched live from Amazon.
What your Keepa requests cost on Logimu.
Volume pricing: the bigger the plan, the less each call costs
| Plan | A month | Credits | Records a month | History lookups a month | Live fetches a month |
|---|---|---|---|---|---|
| Solo | $19 | 25,000 | 50,000$0.38 per 1,0002.9× cheaper | 500,000$0.038 per 1,0002.9–5.8× cheaper | 25,000$0.76 per 1,000 |
| Starter | $50 | 100,000 | 200,000$0.25 per 1,0002.2–4.0× cheaper | 2M$0.025 per 1,0002.9–6.9× cheaper | 100,000$0.50 per 1,000 |
| Growth | $125 | 400,000 | 800,000$0.156 per 1,0002.0–4.1× cheaper | 8M$0.0156 per 1,0003.9–7.9× cheaper | 400,000$0.3125 per 1,000 |
| Standard | $250 | 1,000,000 | 2M$0.125 per 1,0002.1–5.1× cheaper | 20M$0.0125 per 1,0003.9–8.8× cheaper | 1M$0.25 per 1,000 |
| Scale | $1,000 | 5,000,000 | 10M$0.10 per 1,0002.1–4.1× cheaper | 100M$0.010 per 1,0003.4–7.8× cheaper | 5M$0.20 per 1,000 |
| Volume | $3,000 | 20,000,000 | 40M$0.075 per 1,0002.1–5.1× cheaper | 400M$0.0075 per 1,0003.9–10.2× cheaper | 20M$0.15 per 1,000 |
The green ranges compare each figure with Keepa for the same monthly volume on its cheapest plan: the lower number assumes Keepa’s tokens are used around the clock, the higher one a job that runs 8 hours a day. Records are compared with Keepa’s stored offers (5 tokens) and history lookups with its product call (1 token).
Logimu pricing advantage
A Logimu record carries every seller we observed, however many. Keepa charges 6 tokens per page of 10 offers it fetches, or 5 for its stored offers.
Rank, Buy Box and per-seller price history come with the record, or alone for 0.05 credit. Keepa adds 2 tokens per product for Buy Box data on its product call; its offers call includes it.
A monthly allowance you spend when you like, in an afternoon or across the month. Keepa generates tokens around the clock and drops any left unused for 60 minutes, so a nightly job pays for hours it does not use.
A not-found, failed or empty call costs nothing, and mode=live fetches any listing fresh from Amazon for 1 credit. Keepa charges a token even for an ASIN that does not exist.
What else changes when you switch
| Logimu | Keepa API | |
|---|---|---|
| Live scraping | Any listing with every offer, Amazon search pages, Best Sellers lists and seller storefronts, fetched from Amazon when you call | Fresh offers on the product call, 6 tokens per page of 10 offers |
| Product search | A keyword, a UPC or a supplier’s item name becomes ranked, grouped Amazon matches in about 100 ms, typo-tolerant: 2 credits, 12,500 searches a month on Solo. Built for matching supplier lists and for search inside your app. | Product Finder filters, no ranked answers |
| Brand & seller analytics | Brand dossiers, seller maps, category landscapes and ranked lists, computed daily from observed buy-box data | Category and seller objects; no brand endpoint, no brand-to-brand network, no ranked lists |
| Product tracking | Pin an ASIN and its offers page is re-read hourly or every 2, 4, 12 or 24 hours, for as long as the plan is active, each read a point in its buy-box history. Tracking uses no credits: each plan includes a daily number of re-reads, so faster tracking covers fewer products. E-mail and webhook alerts on any tracking: price below or above a value, a price move by percent, a buy-box seller change, offer count, a stock-state change (in stock, no featured offer, out of stock). | Token-priced: a marketplace tracking (buy box, sellers) lowers the plan’s refill by 9 tokens per update per locale, so the count depends on what else the key does; the list is deactivated 7 days after a downgrade; notifyIf webhooks. |
Questions Keepa users ask first.
Which endpoints are there?
Self-serve and metered by credits, live in minutes. Plans from $19/month with an unconditional 14-day money-back. Every Amazon marketplace costs the same, and you are never billed for a request that did not return what you asked for.
The base other product-data APIs sell: every product we observe, with its price, BSR, rating, every seller offer and the buy-box, plus the history behind it — served from the warehouse in milliseconds for half a credit.
Product record & history
Any ASIN’s — or any barcode’s — price, BSR, rating, buy-box and every seller offer, with price and stock change events, buy-box timeline and BSR history on request.GET /v1/product
Curated product search
A keyword becomes ranked, grouped product recommendations in under 100 ms, scored on sales, ratings, reviews and seller signals.GET /v1/shopping
Warehouse filtering
Filter our observed catalogue by price, rating, reviews, BSR, seller count and fulfilment, with the sellers’ feedback records attached.GET /v1/search
CSV batches & schedules
Upload a CSV or POST up to 20,000 ASINs, see the exact credit cost up front, then run it once or on a schedule — CSV or JSON, by download, email or webhook.POST /v1/batches
Price, offer, Buy Box and rank history come with every record at no extra charge. We bill lookups, not time.
When it has to be now: we fetch the page you ask for and return structured JSON in seconds — one credit or less, and only when something lands.
Live product page
mode=live on any product: current price, stock, every offer on the listing, delivery and fulfilment as a local customer sees them.GET /v1/product?mode=live
Live search results
Amazon’s results page the moment you ask: organic grid, sponsored and video blocks, refinements, pagination.GET /v1/serp
Live Best Sellers
Amazon’s Best Sellers list for any category, fetched when you ask: the top 100 in rank order, the category’s full breadcrumb name and its subcategories to walk the tree.GET /v1/bestsellers
Live Today’s Deals
Amazon’s Today’s Deals page, fetched when you ask: each deal’s price next to Amazon’s reference price and its label, percent off, deal type and coupon, and for lightning deals the end time and percent claimed where Amazon shows them. Filter by department, lightning deals, coupons, discount, price, rating, brand or Prime Exclusive; up to 120 deals a page for 1 credit, an empty page free.GET /v1/deals
Live offers page
Every offer on a product’s offers page, fetched when you ask: seller, price, shipping, condition, buy box, FBA or merchant-fulfilled, delivery and the seller’s feedback. By ASIN or barcode, half a credit; or as seen from a US ZIP code, with whether the item is deliverable there (Amazon Fresh and Whole Foods items deliver only to some ZIPs), 1 credit.GET /v1/offers
Product tracking
Pin an ASIN and its offers page is re-read hourly, or every 2, 4, 12 or 24 hours, for as long as your plan is active; every read lands in the product’s buy-box history: price, buy-box seller, fulfilment, offer count. E-mail and webhook alerts on price, buy-box seller, offer count and stock state — every read is recorded as in stock, no featured offer or out of stock, and each change fires. Send up to 1,000 ASINs in one call, or sync your whole list daily. No credits for the tracking — every plan carries a daily allowance of tracked snapshots.POST /v1/track
Seller page & storefront
A seller’s profile as Amazon shows it — rating, feedback by period, business block — and its storefront listing, live or from our seller store.GET /v1/seller
Walmart, same schema
Walmart product data through Akamai Bot Manager: pricing, sellers, BSR and WFS flags as the same JSON shape.GET /v1/product?country=walmart
Eleven Amazon marketplaces plus Walmart US. A blocked or empty fetch is never billed.
What our observations add up to — computed from the buy-box data and the search-suggestion lists we observe, refreshed daily, never estimated. This is the layer the other APIs do not serve.
Brand dossier
How many sellers win the buy box on a brand, Amazon’s own share, FBA penetration, seller concentration and churn, trend grades, benchmarks against its category and the top sellers — with monthly history on request.GET /v1/brand
Seller map
The brands connected to a brand because the same third-party sellers win the buy box on both — weighted edges, node metrics and layout, one hop per call. The graph below is this endpoint.GET /v1/brand/network
Operator footprint
Every brand a seller was observed winning the buy box on, with buy-box days — and the sellers that win on the same brands.GET /v1/seller/brands
Keyword suggestions
What buyers type, as Amazon itself suggests it: the autocomplete suggestion lists we observe for a seed on each marketplace, every term with its position within its list, when it entered and left, and the marketplaces it appears in — across 2–11 marketplaces in one call. Observed suggestion ranking, never volume figures.GET /v1/keywords · /v1/keywords/compare
Category taxonomy — free
Every marketplace’s categories, walked one level at a time, with the ids the landscape call takes and the names the search filter accepts — the marketplace’s own language plus the English alias where we hold one. Any key, never billed.GET /v1/categories
Category landscape & ranked lists
Size, Amazon share, FBA, seller concentration, heat and churn per category; brands gaining or losing sellers; the biggest operators; categories ranked.GET /v1/category · /v1/brands/movers · /v1/sellers/top
1 credit per record, 1 per page of 25 rows, lookups and misses free. Everything is observed, not asserted: “observed since” is our data horizon, never a founding date.
How fresh is the data, and how far back does history go?
History goes back to 2023. On Amazon.com the most-sold listings are re-read at least once a day, the busiest several times a day; a product you track is re-read hourly or every 2, 4, 12 or 24 hours; and mode=live fetches any listing from Amazon on demand for one credit, billed only when it lands. Every record carries its own observed_at and history range, so you always see the age of what you got.
Will it cover my products? Check a list of your ASINs before you pay
Paste up to 10 ASINs below: for each one you see whether we hold it, when it was last observed and how far its price and rank history go. Anything we don’t hold is fetched live from Amazon when you call it (mode=live), billed only when it lands.
observed_at (the snapshot’s own time), bsr_history.observed_from / observed_to, offer_history.observed_from / sellers_total, source (cache or live) and credits_charged. Field reference →What does $19 a month cover?
Credits and tokens are both units. The difference is the mechanism: Keepa’s tokens accrue per minute into a bucket that caps your burst and expire unused; a Logimu plan is a monthly allowance you can spend in one afternoon or across the month, under published request-rate limits. No refill timer in your scheduler.
| What $19 / 25,000 credits a month covers | Per call | Calls / month |
|---|---|---|
| Stored product record with every current seller offer | 0.5 | 50,000 |
… with rank history and seller / Buy Box history (bsr_history, offer_history) | 0.5 | 50,000 |
The history series alone (history_only=true) | 0.05 | 500,000 |
Live fetch of a product page with its offers (mode=live) | 1.0 | 25,000 |
Ranked product search (/v1/shopping): a keyword, a UPC or a supplier’s item name | 2 | 12,500 |
| Brand dossier, seller map, category landscape (derived intelligence) | 1.0 | 25,000 |
Product tracking (/v1/track): re-read hourly to daily, alerts and bulk sync included | 0 | 2,500 re-reads a day |
| Not found, blocked, empty, failed | 0 | — |
History is included in every record, wider series too, as the reference states. Figures assume the allowance is spent on one operation.
What does one product response include?
One ASIN in, the full record out — /v1/product.
- Current snapshot Price, list price, coupon and savings, BSR, rating, review count, stock state, UPC, parent ASIN, brand stats, item dimensions and weight, the variation matrix (child ASINs, dimension values, availability) — and Amazon's own "bought in past month" figure where it publishes one.
- Every seller, in the same call The full live offer list is standard, not a separate endpoint: seller name and ID, price, shipping cost, ships-from, delivery days, FBA and Prime flags, feedback score, buy-box days and the seller’s share of the observed buy-box days. Gathering offers is the slow part of any live scrape, which is why most APIs bill them separately.
- Price and stock history The full price series plus price-change and stock-change events, in the base call — with the list-price, coupon, "bought in past month" and rating-count series alongside.
-
Rank history, per category
Add
bsr_history=truefor daily rank in every category the product sits in. Included in the record, like the seller history below. -
Seller history — who held the buy box, and when
Add
offer_history=truefor a buy-box timeline plus a per-seller price series, each point carrying the seller's shipping cost and FBA flag, with first seen, last seen and buy-box days. Included in the record too. -
Seller profiles, tracked
/v1/sellerreturns the seller page as a record — star rating, feedback per 30 d / 90 d / 12 m / lifetime, the rating histogram, five recent feedback entries (date, rating, struck; never a buyer's name or text) and the business block where Amazon shows one. Every seller we meet is re-read about every two weeks, so the stored record is normally current at half a credit;trackingsays since when and how often we have observed it, andhistory=trueadds the rating-change and storefront-size series. Live fetch for one credit when it has to be now. -
Derived intelligence — the layer Keepa does not serve
What our buy-box observations add up to, refreshed daily and never estimated.
/v1/brandis a brand dossier: sellers observed winning its buy box, Amazon’s share, FBA share, concentration, churn, trend grades and category benchmarks, with monthly history for half a credit more./v1/brand/networkis the seller map — the brands connected to a brand because the same third-party sellers win on both, as weightededges[]andnodes[]with a layout, one hop per credit./v1/seller/brandsturns a seller ID into an operator footprint,/v1/categoryinto a category landscape, and the ranked lists answer “which brands are gaining sellers” or “who are the biggest operators here” at one credit per page of 25. The brand dossier, the network and the lists have no Keepa equivalent. -
Warehouse or live scrape — your call
mode=cacheanswers in under 100ms for half a credit, batch or single call.mode=livescrapes the listing on demand when it has to be current, for one credit. Failed scrapes are never billed.
Eleven Amazon marketplaces plus US Walmart, in one schema, with price, offer and rank history included in every record.
How do Keepa fields map to Logimu?
Each Keepa request and field, and where it is in a Logimu response:
| Keepa | Logimu | Note |
|---|---|---|
GET /product?key=&domain=1&asin= | GET /v1/product?asin=&country=us with header X-API-KEY | domain numbers become country codes (us, uk, de, ca, au, fr, it, es, jp, mx, br) |
csv[0] Amazon price, csv[1] new price | price, price_history[] (change events), offer_history.sellers[].points[] | a daily price series for every seller |
csv[18] Buy Box price | buybox_price_history (offer_history=true) | the lowest Buy Box price of every observed day, Amazon US back to Nov 2023 |
csv[3] sales rank, salesRanks | bsr, bsr_leaf, bsr_history.series[] (bsr_history=true) | daily rank in every category the product sits in |
offers[] (offers=20) | current_sellers.sellers[] — in the base call | name, ID, price, FBA and Prime, feedback, buy-box share, delivery; full_offers=true lists every seller on a live fetch |
buyBoxSellerIdHistory, stats.buyBoxPrice | offer_history.buybox_timeline[], buybox_seller, is_buybox on each seller | who held the Buy Box, from when to when, and who holds it now |
csv[16] rating, csv[17] review count | rating_history.points[] | one point per observed day: Amazon’s ratings count and the star average |
monthlySold | bought_past_month (+ bought_past_month_history) | Amazon’s own badge, as observed |
tokensLeft, refillIn | credits_remaining on every response | no refill timer to poll |
/seller, /category | /v1/seller, /v1/seller/products, /v1/category, /v1/brand | seller profiles and categories, plus brand dossiers and the seller map |
/tracking, notifyIf | POST /v1/track or /v1/product?track=true, notify_if | re-read hourly or every 2, 4, 12 or 24 hours at no credit cost, within the plan’s daily allowance |
Keepa field names from keepa.com/api-docs (product object, read 2026-10-06). Logimu field reference →
The operator network behind a brand, live.
This is the real Nike seller network — every brand below shares Amazon buy-box sellers with Nike, drawn from our observed daily record. The Logimu API serves exactly this object: GET /v1/brand/network?brand=Nike&country=us returns the nodes[] and weighted edges[] you see drawn here, one credit per hop. Hover a brand for its numbers; click one to recenter; type any brand to map it.
Node colour is the brand’s heat (seller pressure: how many sellers per listing and how fast that is rising), size is its catalogue, distance is how many sellers two brands share. Counts and shares from observed buy-box data, refreshed daily — never estimates. Available on every paid plan. Endpoint reference →
Run the same queries from your own code.
Get an API key, query the data you just explored, and keep the 14-day money-back if it does not fit.