Build with Token Supply

Client setup

• Use Codex with a custom API endpoint

  Keep the Codex CLI, app, or VS Code extension you already use. Point the provider at Token Supply, set a plan key, and keep the Responses API.

• Use Claude Code with a custom API endpoint

  Keep Claude Code CLI or the VS Code extension. Replace the Anthropic base URL and auth token with Token Supply, then set reasoning effort.

• OpenCode custom provider configuration

  Keep OpenCode's OpenAI, Anthropic, Gemini, or Grok preset. Replace baseURL and apiKey, set context limits, and use variants for reasoning effort.

• Configure Cursor with an OpenAI-compatible API

  Keep Cursor's OpenAI preset. Paste a Token Supply key, turn on Override OpenAI Base URL, and choose a model from that key's plan.

• Use the OpenAI SDK with a custom base URL

  Keep the OpenAI SDK, curl, or any OpenAI-compatible client. Change the API key and base URL. The model must belong to the plan on that key.

• Use the Anthropic SDK with a custom base URL

  Keep the Anthropic SDK. Change the API key and base URL. Claude Code uses the same host; do not add /v1 to ANTHROPIC_BASE_URL.

• Configure Hermes with an OpenAI-compatible API

  Keep Hermes's custom endpoint setup. Replace the base URL, set the context window, and store the Token Supply key in .env.

• Write client config files from the terminal

  A setup CLI is coming soon. Until then, create a key in API Keys and paste the values from the matching client guide.

Start here

Create an account, add credit, create a plan key, and point your client at Token Supply. Dedicated setup pages cover each client.

Codex · Claude Code · OpenCode · Cursor · OpenAI SDK · Anthropic SDK

Related

• AI API token cost calculator — Compare listed Token Supply rates with public list prices.
• Reduce coding-agent API costs — Keep your client and lower token spend on the same workload.
• Track AI API token usage — Prepaid wallet, usage dashboard, and per-key spend.