Point the Anthropic SDK at apiToken.sale

One argument switches the endpoint

Both official Anthropic SDKs — Python and TypeScript — let you override the API root when you construct the client. Set it to https://router.apitoken.sale and every request your code already makes is served by apiToken.sale's gateway instead of api.anthropic.com. Nothing else in your codebase moves: same anthropic package, same Messages API, same model IDs like claude-opus-4-8, same response objects.

What changes is billing. Each call is metered at official Anthropic token rates, your flat 50% discount is subtracted, and the net amount is drawn from a prepaid balance you top up in whole-dollar amounts. No subscription, no per-seat fee — idle days cost nothing.

See also: Claude API quickstart: set up and make your first call

Python: base_url on the client

from anthropic import Anthropic

client = Anthropic(
    base_url="https://router.apitoken.sale",
    api_key="sk-pool-•••",
)
msg = client.messages.create(
    model="claude-opus-4-8",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Hello"}],
)

The async client takes the identical keyword: AsyncAnthropic(base_url=..., api_key=...). Streaming via client.messages.stream, tool use, system prompts and prompt caching all ride on the same connection — there is no separate endpoint to configure for them.

Pass the bare root, not a path. The SDK appends /v1/messages itself, so base_url=".../v1" produces requests to /v1/v1/messages and a 404. The same rule applies to the TypeScript SDK.

TypeScript: baseURL on the client

import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic({
  baseURL: "https://router.apitoken.sale",
  apiKey: "sk-pool-•••",
});
const msg = await client.messages.create({
  model: "claude-opus-4-8",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Hello" }],
});

The @anthropic-ai/sdk package sends the x-api-key and anthropic-version headers for you, exactly as it does against the official endpoint. Retries, timeouts and error classes (APIError, RateLimitError and friends) behave identically, so existing error handling keeps working.

Prefer environment variables in shared code

Both SDKs read ANTHROPIC_BASE_URL and ANTHROPIC_API_KEY from the environment when the constructor arguments are absent. That makes the switch a deployment detail instead of a code change — useful when the same repository runs against different endpoints in development and production.

export ANTHROPIC_BASE_URL=https://router.apitoken.sale
export ANTHROPIC_API_KEY=sk-pool-•••

# your code now constructs Anthropic() with no arguments

Tools built on top of the SDK inherit the same variables. Claude Code, for example, honours ANTHROPIC_BASE_URL and ANTHROPIC_API_KEY directly, and frameworks like LangChain or LiteLLM forward the same environment to their Anthropic client underneath. Explicit constructor arguments win over environment variables when both are set, so a one-off override in a script never leaks into your deployed configuration.

What crosses the gateway unchanged

• The full Messages API surface: POST /v1/messages with the same request and response JSON.
• SSE streaming — incremental chunks arrive exactly as from api.anthropic.com.
• Tool use and function calling, including multi-turn tool_result loops.
• System prompts, vision inputs and prompt caching with cache_control breakpoints.
• The usage object on every response, so your token- and cost-tracking code keeps working.
• Model IDs: claude-opus-4-8, claude-sonnet-5, claude-haiku-4-5 and the rest of the supported catalog.

One key covers every supported model — Claude alongside GPT, Gemini and Kimi — so a multi-provider project keeps a single credential and a single balance. Per-request spend and the applied discount are visible in the dashboard after each call.

Supported model IDs and per-model pricing →

Estimate monthly spend in the cost calculator →

First-request checklist and common errors

1. 01Create a free account, open the dashboard and generate a key — it looks like sk-pool-… and works across the supported Claude, GPT, Gemini and Kimi models.
2. 02Set base_url / baseURL to https://router.apitoken.sale in code, or export ANTHROPIC_BASE_URL and ANTHROPIC_API_KEY.
3. 03Run the Python or TypeScript snippet above once and confirm you get a normal Anthropic message response.
4. 04Open the dashboard and verify the request appears with its token usage, cost and discount.

Because the SDK, the wire format and the error taxonomy are identical on both endpoints, the switch is reversible at any time: point base_url back to api.anthropic.com (or delete the override) and the same code talks to Anthropic directly again. Many teams keep both clients constructed side by side during a migration week and route a small percentage of traffic to the new endpoint before flipping fully.

Existing integrations on the legacy https://api.apitoken.sale host keep working. The unified router at router.apitoken.sale is the recommended endpoint for new setups because one base URL serves all four providers.

Frequently asked questions

Related guides