How Can We Help?

A successful result is billed. A freshly crawled "not found" is billed too, because we still did the work of checking. A "not found" re-served from the not-found cache, and any failed request, cost nothing. For most sources 1 credit delivers a full data set for one SKU. On Amazon, Walmart, and eBay, 1 credit delivers 2 full data sets (search + product + offers, matched, each). Kaufland costs 3 credits per result, reflecting its higher delivery cost. Pricing overview.

Every freshly crawled not-found is billed, and re-checks within the cache window are free. Once we confirm a product is not found we remember it, so repeat checks inside the window are answered from the not-found cache with no crawl and 0 credits. The window is 10 days by default and adjustable per request with not_found_max_age; after it passes, the next check triggers a fresh crawl and is billed at the source's normal rate. API documentation.

A "not found" costs 0 credits when it is re-served from the not-found cache, which is honoured for 10 days by default and adjustable per request with not_found_max_age. A failed request and a cached response cost 0 credits too. A freshly crawled "not found", one we had to crawl to determine, still costs 1 credit, because we still did the work of looking.

No. Credits roll over and never expire. There's only one kind of credit; there are no separate packs to buy.

Retry two things: a 503 response, after the interval in its Retry-After header, and any value whose result reason is "source currently unavailable", by re-submitting it in a later job rather than instantly. Do not retry validation errors, 401, 403 or 402, they will keep failing until something changes on your side. Use exponential backoff with a finite attempt count for network-level failures. Robustness guide.

It depends on what the charge was for. If it's your subscription, your account keeps working normally for 7 days while we retry the card; nothing pauses immediately. If it's an overage charge, we retry automatically and your account keeps a small allowance to stay working in the meantime, so a single payment blip never interrupts your integration.