Register and Save Your API Key
Register with an email address and a password of 12 to 72 bytes. Successful signup displays your API key once, immediately and before payment. Save it before leaving that screen, because it is not delivered by email or available for later redisplay. Signup does not require Google login, a wallet connection, or entering a wallet address.
An eligible account may receive an optional 100-credit trial, subject to network-wide anti-abuse limits. Check the account panel on this key page for the balance available to your account; obtaining a key does not guarantee trial eligibility. If you need a replacement key, sign in and confirm your password. Regeneration immediately invalidates the previous key, so update your applications before making further requests.
Pricing and Top-Up Procedures
Retrieving data costs one credit per successful request, including empty results. Invalid requests do not debit credits, while upstream retrieval failures refund reservations. A connection failure at the client can follow successful, billable server retrieval; a successful retry costs another credit. The rate is $1 per 1000 successful requests, with a $50 minimum paid top-up. Sign in and create an invoice, then use its exact amount and receiving address with USDT TRC20 or USDC ERC20 on the Ethereum mainnet.
After sending the invoice payment, paste the transaction hash into the verification panel. The server must verify a confirmed genuine transfer before adding credit. Follow the current invoice instructions for the receiving address, exact amount and token network. Do not treat invoice expiry as a confirmation or Verify-click deadline. Verification does not carry a fixed completion-time or immediate-crediting guarantee.
Service Terms and Data Handling
This is an independent historical archive, not an official Reddit service. It supports standard queries across posts, comments, and subreddits without requiring live data from the official platform. The archive is stored in document order, which differs from chronological or relevance sorting, and limits results to one hundred records per request. Pagination allows up to one hundred pages, but iteration does not guarantee complete coverage of all available historical data.
Account data includes your email, password hash, API key hash, abuse-prevention IP information and payment transaction records. Pages use Statinside analytics. Sessions use a Secure HttpOnly cookie, while per-host localStorage holds invoice and user IDs; the raw API key is not persisted there. Keep credentials out of shared source code and review the privacy policy before integrating the account workflow into your development process.
