Simple credits.
Current beta options.
Compare the currently published options for cache-aware inventory requests. Every plan includes durable public page snapshots and explicit refresh behavior.
One predictable balance,
clear charges per page.
Each plan includes a monthly credit allocation equal to its published monthly request ceiling. Every successful inventory page and confirmed private result is priced independently; only modes that force a fresh Steam fetch add a credit.
1 credit for a successful HIT, MISS, or STALE response, or for a confirmed private MISS or HIT.
no_cache=true adds 1 fresh-fetch credit: any Steam session costs the same, and both together cost 2 credits total.
steam_login_secure or X-Steam-Login-Secure bypasses the shared cache and costs 2 credits for a billable result, including a confirmed Steam HTTP 403.
Fresh modes do not stack. Filters, pretty JSON, identifiers, and cursors add no credits. Failed requests and non-authoritative success=false results cost 0; confirmed private inventories use the normal 1- or 2-credit quote.
Before you
make a request.
01What counts as one request?+
A successful normal public page or confirmed private MISS/HIT costs 1 credit. A billable fresh cache bypass—with no_cache=true, with any Steam session, or with both together—costs 2 credits total, including when Steam confirms privacy with HTTP 403.
02Are inventory results cached?+
Yes. Normal public requests can reuse durable page snapshots. no_cache=true forces a refresh, while requests carrying a Steam session bypass the shared cache.
03Can I change plans later?+
Yes. During the private beta, contact support and we will move the account without rotating your API key.
04What happens when credits run out?+
The API returns HTTP 402 with a stable insufficient_credits error. Existing credentials remain valid; during the beta, contact support about the next allocation or plan.