🐰 RabbitCode

DOCUMENTATION · Updated September 27, 2026

Connect your tools.
Check your first request.

Set up an account, create an API key and verify your client connection. These instructions cover configuration and troubleshooting.

1. Create your account and API key

  1. Register or sign in to your existing account.
  2. Check the available balance or active plan in the console. If you received a redemption code, redeem it in your account.
  3. Open API keys and create a key for your client.
  4. Keep the key private. Do not paste it into screenshots, public repositories or support messages.

Account registration, available balance and an API key are separate steps. A successful login alone does not verify that a model request will succeed.

2. Configure Claude Code

For an already installed Claude Code client, configure the custom endpoint using the environment variables below. Use a model ID supported by your account. Check the installed client's current documentation if its configuration differs.

macOS / Linux

export ANTHROPIC_BASE_URL="https://rabbitcode.top/claude"
export ANTHROPIC_AUTH_TOKEN="YOUR_RABBITCODE_API_KEY"
claude

Windows PowerShell

$env:ANTHROPIC_BASE_URL="https://rabbitcode.top/claude"
$env:ANTHROPIC_AUTH_TOKEN="YOUR_RABBITCODE_API_KEY"
claude

These commands apply to the current terminal session. For persistent settings, use the client's configuration file or your operating system's environment-variable settings. Avoid configuring conflicting API key and authentication-token values.

Verify the connection

Send a short, non-sensitive request. Then open the console's usage page and confirm a new successful request and the resulting usage. If there is an error, use its status code below. Do not print your secret key to check configuration.

3. Configure another client

ClientConfiguration
Roo Code / Kilo CodeSelect the Anthropic-compatible provider, set the custom base URL to https://rabbitcode.top/claude, and enter your RabbitCode key.
Cherry StudioAdd an Anthropic-compatible provider with the same base URL, then load the model list supported by your account.
Other compatible toolsCheck whether the client expects a base URL with or without /v1. Avoid adding /v1 twice.

Client compatibility depends on the client version and request format. Test one short request before starting a long session.

The Codex compatibility endpoint remains experimental. Gemini CLI is not currently supported by the existing setup guide. Do not assume that every client feature is available.

4. Check your plan and payment

Review the plan shown in your account before purchasing: the actual payment amount and currency, included allowance or request count, expiry time and any rate limits. Dollar-denominated usage values and the amount you pay may represent different things.

If your account offers online checkout, follow that checkout flow and return to the console to verify the order status and delivered entitlement. Some accounts may not have access to online purchasing. Contact support@rabbitcode.top if the option you need is unavailable.

A payment-return page does not by itself prove that a payment succeeded. Confirm the paid order and the corresponding balance or redemption code. See the terms of service for billing and refund information.

5. Troubleshoot a failed request

StatusWhat to check
400Request format and supported parameters.
401Key validity, authentication settings and endpoint.
403Account and key permissions.
404Endpoint path and supported model ID.
413Reduce the request size or conversation context.
429Stop repeated retries. Check your allowance and rate limit, then retry later.
500 / 529Service or upstream failure. Retry later and contact support if it persists.

For support, include the time, client/version, status code and a redacted request ID if available. Do not include API keys, passwords or private source code.

Website measurement

We use self-hosted analytics to understand page visits, referral campaigns and a small number of account actions. These analytics do not receive your API key, email address, prompts or source code. Do Not Track and Global Privacy Control signals are respected. See our privacy policy.