Start with the right credentials.
A redemption code starts with TSL-. It represents a package from your seller. An API key starts with sk-. Your coding tool uses the API key to make requests.
Redeem a new code or check your existing key before configuring a tool. Save the key and original code in a password manager. Neither should be posted in chat, screenshots, public repositories, or support tickets.
Connect your coding tool.
Select your tool and operating system. Model availability depends on your key, not the name of the client.
1. Install the CLI
Install a current Node.js LTS release, then install Codex:
npm install -g @openai/codex2. Set your API key
This keeps the key out of the configuration file and shell command history. It applies to this terminal session.
$creditSecret = Read-Host "API key" -AsSecureString
$env:CREDIT_API_KEY = [System.Net.NetworkCredential]::new("", $creditSecret).Password3. Configure your provider
Back up your existing configuration. Add or merge the following into your user-level file: %USERPROFILE%\.codex\config.toml. Provider routing belongs in the user configuration.
model = "<MODEL_ID_ALLOWED_FOR_YOUR_KEY>"
model_provider = "credit_gateway"
[model_providers.credit_gateway]
name = "Credit Gateway"
base_url = "<BASE_URL_FROM_YOUR_SELLER>"
env_key = "CREDIT_API_KEY"
wire_api = "responses"
requires_openai_auth = false4. Open Codex
Run codex in this terminal. Select a model allowed by your package. Actual model requests consume credits.
VS Code and Codex Desktop
The official Codex extension and supported desktop builds can use user-level provider configuration. Install the official extension and fully restart the editor. The API key environment variable must be available to the application process.
For a newly launched Windows application, persist the variable in your user environment, then reopen the application:
[Environment]::SetEnvironmentVariable("CREDIT_API_KEY", $env:CREDIT_API_KEY, "User")On macOS, a GUI application does not automatically inherit terminal variables. Consult the official gateway guide for environment setup. On Linux, launch the editor from the configured terminal. Desktop support depends on the build, gateway features, model metadata, and local policy; cloud and subscription features are separate.
Use another API client.
Choose an OpenAI-compatible or Anthropic-compatible client that supports a custom base URL and the protocol your package supports. Codex requires the Responses protocol. Claude Code requires an Anthropic-compatible Messages endpoint. Do not append a second /v1 or remove a required path.
The endpoint below is a placeholder; obtain the real value from your seller. This example lists models; it does not generate output. Run it in bash after setting CREDIT_API_KEY using the guide above.
export CREDIT_BASE_URL="<BASE_URL_FROM_YOUR_SELLER>"
curl --fail-with-body "$CREDIT_BASE_URL/models" \
-H "Authorization: Bearer $CREDIT_API_KEY"Use the exact model ID from the response or the checker. A model ID describes the route offered by the service; it does not independently verify model provenance.
Understand what your balance means.
The checker displays the provider’s customer-facing token allowance, or points for image packages. It never converts internal quota units into tokens. Input, output, reasoning, caching, and model-specific consumption can affect the balance; use your package’s current terms for the applicable rules.
Used, remaining, and total values are reported separately. They may differ from a simple subtraction because of accounting rules or timing. Unlimited allowance and permanent expiry are shown explicitly. Missing data is labeled rather than estimated.
A compatible top-up adds credits and extends expiry from the later of the existing expiry and now. An eligible expired or exhausted key is reactivated. A provider-disabled key cannot be topped up. Product families must match; an Astra code and a GPT key are separate families.
Rate limits restrict requests per minute. A high credit balance does not remove these limits. Usage history is paginated in groups of ten and shows reported requests only.
A clear next step when something stops.
My code was already used
Choose Check outcome on the redemption page. A used code can recover its associated key. For top-up, enter the same key and code so the portal can verify that the code was applied to that exact key.
A redemption or top-up timed out
Do not submit another top-up. Use Check outcome. After an uncertain attempt, wait at least a minute before checking an unused result again. A code held for manual review must be reviewed by the seller or provider.
401 · unauthorized
Check the complete key and configured endpoint. Use the key, not the TSL code. For Claude Code, confirm Bearer authentication is configured using ANTHROPIC_AUTH_TOKEN. Check expiry and status.
429 · too many requests
Pause for the stated retry period. Reduce parallel requests. The portal also has a shared upstream request budget, so a busy service may need a minute before another check.
404 · wrong route or unavailable model
Check the exact base URL, avoid a duplicate /v1, and select a model returned for your key. A model supported by one package may be absent from another.
500, 502, 503, 524 · service unavailable
Check again later. For a credit-changing operation, recover the original outcome first. For model requests, follow your client’s retry guidance and account for possible usage.
The balance dropped faster than expected
Agents resend conversation context and tool output. Large files, long sessions, retries, and reasoning can consume more credits. Compare the checker’s reported activity with your client.
The security check will not load
Allow the verification widget from Cloudflare, check your connection, and reload the page. Do not send your key to a CAPTCHA-solving service.
I need help from my seller
Send the operation, approximate UTC time, non-secret error text, and portal reference if shown. Do not include your API key or complete code in an ordinary ticket. Ask for an approved secure channel if the provider needs a code for manual review.
Official references.
General client configuration is documented by the tool developers. Endpoint and package support depend on the connected service.
- Codex configuration
- Codex Desktop gateway setup
- Claude Code gateway setup
- Claude Desktop third-party inference
Reviewed 13 November 2026. Package-specific client connections have not been live-tested in this project.