Make the credential handoff deliberate
Choose where your SaaS backend will read its secret before registering. The key belongs in server configuration, not in the research view sent to a customer. Give the person doing setup a way to save it securely at the moment it appears; a screenshot in a shared issue is not a useful handoff.
The teammate wiring the feedback view into your SaaS registers the archive account with an email and a password of 12–72 UTF-8 bytes. Count encoded bytes rather than visible characters. Signup provides no Google login and needs neither a wallet connection nor a wallet address. Immediately after successful signup, before payment, this page displays the key once. Transfer it into the prepared secret store for the backend; it remains reusable even though it will not be emailed later or shown again at login. Check the account’s actual starting balance separately: the possible 100 trial credits depend on network-wide anti-abuse eligibility. The people reading the SideProject excerpts should receive those texts through your application, not this credential.
Connect the account to the right application
This page's account panel manages redditapicloud.com. Its key and balance do not transfer to other domains. Use Authorization: Bearer <key> or X-API-Key: <key> for retrieval; both are supported. Your signed-in website session is separate from those headers and from your SaaS users' own permissions.
Once credits are available, run the homepage's feedback search in SideProject with limit=3 from the backend. Check that one authorized action produces a readable result or an accurately labelled empty state. A successful empty response also consumes one credit. Do not treat the public /v1/status response as a check of the key or archive availability.
Fund the pilot from the current invoice
Treat funding as a step in preparing the feedback-research pilot, after deciding which backend will make its requests. The first paid top-up is at least $50 for 50000 credits, priced at $1 per 1000 successful retrievals. Purchased credits do not expire and there is no subscription. The account operator signs in here and creates a server invoice before sending funds. Use its current recipient and exact amount with USDT on TRON TRC20 or USDC on Ethereum mainnet ERC20. Submit the transfer’s transaction hash for verification; credits require a genuine confirmed transfer matching that invoice. A payment receipt alone does not show that your SaaS displays the returned text correctly.
The invoice lasts one hour; settlement time is not guaranteed and provider outages can leave verification pending. Pending does not mean pay again. When credits are available, try the homepage search for feedback in SideProject and inspect the response before exposing the feature to your users. Each successful retrieval, including empty data, costs one credit. HTTP 401 concerns credentials, 402 the balance and 429 rate limits. Public /v1/status does not validate your key or search availability.
Keep replacement separate from troubleshooting
If you lose or expose the secret, sign in and confirm your password to regenerate it. The previous key stops working immediately, so update each backend configuration that used it. There is no password-reset or emailed-key feature. If the key is intact, inspect request errors and the balance before rotating it as a guess: changing credentials does not fix an invalid query or replenish credits.
The widget keeps invoice and user identifiers in localStorage per hostname for invoice recovery, not the raw API key. Keep the saved application secret under your own control. The guide explains how to test the feature without multiplying paid retries; pricing details remain available on the pricing page.
