Signup and Key Generation
Create an account with an email address and a password of 12 to 72 bytes in UTF-8. Some characters use more than one byte. There is no Google login or wallet connection step. The account panel is on this key page, where you can sign in, inspect your balance and create payment invoices without a separate dashboard address.
Successful signup displays the API key once, immediately and before payment. Save it in your secret store before leaving that screen: it is not emailed or redisplayed later. An eligible account may receive a conditional 100-credit trial under network-wide anti-abuse limits. Check your available balance before sending the first schema-inspection request; receiving a key does not guarantee trial eligibility.
Payment and Verification Process
For paid credit, sign in and create an invoice before transferring funds. The rate is $1 per 1000 successful requests, with a $50 minimum top-up for 50000 credits. Paid credits do not expire and there is no subscription. Choose USDT TRON TRC20 or USDC ERC20 on Ethereum mainnet, then use the current invoice receiving address and exact amount.
After payment, paste the actual transaction hash and request verification on this page. Credit is added only after the server verifies a confirmed genuine transfer matching the invoice. The invoice expires one hour after creation; follow its transfer instructions. No fixed confirmation or crediting time is promised. Unavailable provider information may leave verification pending, rather than establishing that payment failed.
Key Management and Security
To replace a lost or exposed key, sign in and confirm your password. Regeneration immediately invalidates the previous key, so update the secret in your loader before the next request. Password reset and emailed key delivery are not provided. The key and balance belong to redditdataapi.com, and a key from another site in the network will not authenticate here.
Keep retrieval credentials in server configuration, using X-API-Key or Authorization: Bearer. The account session cookie serves a separate purpose. The widget stores invoice and user IDs per host in localStorage, not the raw key. Each successful retrieval, including an empty result, costs one credit; invalid requests do not debit and upstream failures refund reservations. Review the documentation before committing warehouse loads.