Budget successful requests for a bounded collection

One credit per successful retrieval, including empty results. Minimum $50 for 50000 paid credits; no subscription or expiry for purchased credits.

Get API key

The unit of cost

Pricing is straightforward: you pay one credit for every successful retrieval request. Each request retrieves a maximum of 100 records, ensuring efficient data extraction without unnecessary overhead. Even if a query returns an empty result, it still consumes one credit, reflecting the server resource usage for processing the request regardless of the output volume. The rate is $1 per 1000 successful requests, or $0.001 per credit. The minimum paid top-up of $50 adds 50000 credits; it is not required for signup or key issuance. There are no subscriptions and purchased credits do not expire. Public /v1/status is uncharged.

A sample built using 15 successful page requests consumes 15 credits, even if the study's inclusion rules later exclude every record. Additional pages, item lookups and successful repeats each have their own cost. Local reprocessing of a saved response makes no new archive request. Conditional 100 trial credits depend on network-wide anti-abuse eligibility; they are not a guaranteed purchase bonus. Signup displays the key before payment.

Failures, retries and page boundaries

Invalid requests do not debit credits; upstream failures refund the reserved credit. A lost client response is different and may follow a successful charged retrieval. Another successful attempt costs another credit. Your own mapping or storage failure does not establish that the upstream request failed. Include successful empty pages and integration tests in the budget, rather than counting only rows eventually stored in your application.

At most 100 records fit in one request, and a query allows at most 100 pages, requested separately. Those caps do not prove full coverage. HTTP 402 concerns an insufficient balance; 429 concerns rate limiting. /v1/status is public and uncharged but exposes neither account balance nor refund history. Accounts, keys and balances belong to redditcollector.com rather than a shared network account.

Current invoice payment

Sign in to the account panel on the key page and create an invoice before transferring funds. Accepted options are USDT on TRON TRC20 and USDC on Ethereum mainnet ERC20. Use the exact amount and recipient displayed in that invoice. Separate invoices do not imply new recipient wallets. Incorrect amounts, tokens or networks may be ineligible; eventual credit, recovery or refund is not promised.

The invoice expires after one hour. After sending, paste the transaction hash and request verification. Credit requires server verification of a genuine confirmed transfer matching the invoice, without a guaranteed settlement duration. A provider outage can leave verification pending. Do not send a second payment merely because a check remains pending. Follow the account panel’s current invoice state rather than expecting a retrieval endpoint to track payments.