Bring a small reading plan to the account panel
Before registering, choose the first worksheet row: transit in urbanplanning with limit=3. Leave room for a housing row, but do not fetch extra pages merely to fill it. This pilot checks whether the available text and fields can support your question. Put query conditions in a shareable file and reserve a separate secret store for the credential; a colleague reviewing the research does not need your account access.
Save the once-shown credential
Register using your email and a password containing twelve to seventy-two bytes. Google login is not supported, and no wallet connection is required. Upon successful signup, your unique API key is displayed immediately on this page before any payment occurs. This key appears exactly once, so you must save it securely. It is not sent to your email or stored in browser local storage.
The password limit is measured in UTF-8 bytes, not characters; some characters use several bytes. Ordinary login does not show the full key again. A signed-in user can regenerate it after confirming the password, immediately invalidating the previous key. There is no password-reset feature. Keep the password and key in an appropriate secret store rather than in the worksheet you share with other analysts.
Connect your reader without sharing the secret
Your research program uses X-API-Key with the raw secret or Authorization: Bearer with the same secret. The website session uses a Secure HttpOnly cookie. The payment widget saves only user and invoice identifiers in localStorage per hostname; it does not persist the raw key, password, transaction hash, amount or full invoice. Do not include secrets in screenshots or logs shared for troubleshooting.
Use https://api.subredditdata.com/v1/search?q=transit&subreddit=urbanplanning&limit=3 for the first retrieval and retain the actual outcome beside the worksheet row. A 401 response is an access problem, 402 concerns the balance, and 429 concerns request frequency. None is evidence that transport was absent from the community. If you regenerate the key, update your private client configuration before continuing the comparison.
Fund only the retrievals you decide to make
The key and balance belong to subredditdata.com. A separate optional 100-credit trial depends on network-wide anti-abuse eligibility and is not assured for every signup. Each successful retrieval uses one credit, even with no records. $1 buys 1000 paid credits and the $50 minimum top-up adds 50000; paid credits do not expire and there is no subscription.
After login, create an invoice for USDT TRC20 on TRON or USDC ERC20 on Ethereum mainnet. Follow its current recipient, exact amount, token and network, without rounding or assuming a changing address. The invoice expires one hour after creation; this is not a promise about payment confirmation speed. Submit the transfer hash after payment and wait for server-confirmed status rather than treating the submission itself as credit.
A lost client response can still belong to a successful, charged server request; a successful retry consumes another credit. An upstream failure refunds the reservation. Keep uncertain attempts separate from successful empty results in your notes. That distinction protects the interpretation of the pilot as well as the request budget.
