Skip to main content
One base URL covers every provider Toolken supports. You keep using the SDK you already have. The gateway detects which provider to call, forwards your request, and returns the response unchanged.

​
How it works

Your app sends a request to https://gateway.toolken.ai/v1. The gateway reads the model name, picks the right provider, attaches your provider key, and forwards the call. Your cost and usage land in the dashboard.
One edge hop. No extra infrastructure. No per-provider glue code.

​
Supported providers

OpenRouter model names use vendor/model notation that overlaps with real provider prefixes, so auto-detection is intentionally disabled. Always set X-Toolken-Provider: openrouter when routing through OpenRouter.

​
BYOK: you own your keys

Toolken does not pool or hold provider credentials. You send your own provider key on every request. The gateway forwards it verbatim and never stores it. You keep full control of your provider account and billing relationship. See Authentication for the two-key model.

​
OpenRouter: hundreds of models through one provider

Setting X-Toolken-Provider: openrouter routes your request to OpenRouter, which aggregates hundreds of upstream models under a single OpenAI-compatible surface. It is a convenient way to reach models from providers not listed above or to compare outputs across providers.

​
Next

Choose a Provider

How the gateway picks a provider, and how to override it with X-Toolken-Provider.

Anthropic & Gemini

Using Anthropic’s native Messages API and Gemini through the OpenAI-compatible endpoint.