Budget for Community Research Requests
Pay $1 per 1000 successful retrievals, including empty results. Minimum paid top-up: $50 for 50000 credits. Conditional trial and invoice payment details.
Get API keyOne credit per successful retrieval
Each successful retrieval request costs one credit, including a successful search with no matches. The rate is $1 per 1000 requests, or $0.001 per credit. Up to 100 records may be returned, but records are not a separate billing unit. Each additional page and each successful repeat counts as another request, regardless of how many passages you later code locally.
The minimum paid top-up is $50, buying 50000 credits. Paid credits do not expire and there is no subscription or recurring renewal. The minimum is a purchase requirement, not a balance you must maintain. Estimate the cost of gardening samples, comparison-community pages and successful retries separately. Equal request budgets do not guarantee equally sized samples or equivalent archive coverage for the two communities.
Trial balance and invoice creation
Signup displays your key once immediately, before payment. An eligible account may receive 100 trial credits under network-wide anti-abuse controls; allocation is not guaranteed. Check the actual balance in the account panel before scheduling requests. Those conditional credits are distinct from the paid credits purchased with $50. Registration and receiving a key do not require a deposit or wallet connection.
To buy credit, sign in and create an invoice before sending funds. Choose USDT on TRON TRC20 or USDC ERC20 on Ethereum mainnet. Follow the current invoice for the exact amount and recipient. A unique invoice identifier does not imply a new or rotating wallet. Check the token and network carefully; no wrong-network recovery or manual crediting service is supplied.
Verification and failed attempts
After the transfer, paste its transaction hash and request verification. The server adds credit after verifying a confirmed genuine transfer matching the invoice. The invoice expires one hour after creation; follow its current transfer instructions. Expiry is not a deadline for clicking Verify or a settlement promise. Provider outages may leave verification pending. No fixed confirmation or crediting time is guaranteed.
Invalid requests do not debit credits and upstream failures refund reservations. A client connection interruption can follow a billable server success; another successful request costs another credit. The public /v1/status route is uncharged, but does not test search or record availability. The key and balance belong to subredditapi.com, so purchased credit on another brand in the network does not fund this comparison.
