Credit units and example costs
Each successful retrieval costs one credit, including an empty result. At $1 per 1000 successful requests, a credit costs $0.001. Minimum paid top-up is $50 for 50000 credits. There are no subscriptions and paid credits do not expire. You buy request credits, not a guaranteed number of useful comments, complete conversations or permanently available records.
For example, 12 successful page requests consume 12 credits whether your mapping keeps every record, rejects some fields or receives empty data. Each successful repeated request costs another credit. A conditional 100-credit trial depends on anti-abuse eligibility across the network and is not guaranteed for every signup. The API key is shown before payment; the minimum applies to paid top-ups, not key issuance.
Plan for uncertain client outcomes
Invalid requests do not debit credits, and upstream failures refund the reservation. Your client can nevertheless lose a response after the server has completed a charged retrieval. A local timeout is not proof that nothing was billed. Keep outcomes distinct and budget successful retries separately. Reusing a saved response in your own cache does not itself require another retrieval request.
Retrieval allows at most 100 records per request and 100 pages per query, one page per request. Those limits do not establish complete coverage. HTTP 402 means insufficient balance, while 429 means rate limiting rather than a known trial-abuse condition. /v1/status is public and uncharged but does not reveal your balance or refund history. Accounts, keys and balances are specific to redditfetch.com.
Pay from a current server invoice
Sign in to the account panel on the key page and explicitly create an invoice before sending funds. Use its exact amount and recipient with USDT on TRON TRC20 or USDC on Ethereum mainnet ERC20. A separate invoice does not imply a new wallet address. Unsupported tokens or networks are not promised a pending recovery or refund workflow.
The invoice expires after one hour. After sending, paste the transaction hash and request verification. Credits require server verification of a genuine confirmed transfer matching the invoice, without a guaranteed settlement time. A provider outage can leave verification pending; this is not an instruction to send the payment again. Use the account panel to review invoice state rather than expecting the retrieval status route to track payment.
