Prepare access to the fragments you want to read

Prepare a small learnprogramming retrieval, keep account credentials separate from comment annotations, and manage domain-specific credits and invoices.

Get API key

Define the first reading session

Start with a bounded task: inspect the text and available relationship fields in the learnprogramming example before planning a larger collection. The key grants retrieval access; it does not unlock a complete thread or a teaching-quality classifier. Decide what you need to read first so an unresolved reference does not automatically trigger an open-ended search.

Register with an email address and a password of 12–72 UTF-8 bytes. Bytes are not the same as characters: some characters occupy several bytes. Google sign-in, wallet connection and email delivery of keys are not part of this workflow. The API key appears once immediately after successful signup, before any payment, so save it securely at that moment.

Authenticate the retrieval, not the interpretation

Send X-API-Key: <key> or Authorization: Bearer <key> from your server; both work. Keep the secret out of annotated transcripts and shared code examples. Account login is a separate session, not a substitute for the retrieval header. Record the request and its outcome alongside the saved response so your team can distinguish a new retrieval from a local rereading.

The account panel remains on this key page. It shows your balance and manages invoices and key regeneration for redditcommentsapi.com. Keys and balances are domain-specific. A conditional 100-credit trial is subject to anti-abuse eligibility across the network, so receiving a key does not guarantee trial credits. Paid credit starts with a minimum $50 top-up for 50000 credits.

Replace access without rewriting the evidence

A signed-in user can regenerate the key by confirming the account password. This immediately invalidates the old key, so update any applications that used it. The original secret cannot simply be redisplayed later. Try the homepage learnprogramming request with a small limit when credits are available. Every successful retrieval, even empty, costs one credit; a successful retry costs another.

Changing a credential does not change a saved comment or justify a different annotation. Keep the original passage and your notes separately from access configuration. The widget stores user and invoice identifiers per host in localStorage, not the raw API key; account sessions use a Secure HttpOnly cookie. There is no password-reset or emailed-key workflow.

Add credit when another retrieval is needed

Sign in, create an invoice, then send the exact displayed amount to its displayed recipient using USDT on TRON TRC20 or USDC on Ethereum mainnet ERC20. Submit the transaction hash to request verification. The invoice expires in one hour. Credit depends on a genuine confirmed matching transfer, and provider unavailability can leave verification pending; do not pay twice because a check is pending.

The price is $1 per 1000 successful retrievals, with no subscription or paid-credit expiry. HTTP 401 means missing or invalid API authentication, 402 insufficient credits and 429 rate limiting. Public /v1/status is uncharged and does not validate your credentials or search backend. Read the documentation for request limits and the guide for the limits of local relationship reconstruction.