Forge
Sign in
Advanced

Bring your own keys

BYOK lets you register provider credentials with Forge. Forge routes the request, handles retries and observability, and never bills you for the tokens — you pay the upstream provider directly.

Why BYOK

  • Use existing enterprise contracts and committed-use discounts.
  • Keep usage on your own provider account for compliance.
  • Still get unified billing, quotas, eval suites, and routing.

Register a channel

Open Channels in the console and click Add channel. Pick the vendor, paste your provider key, and optionally pin a base URL (for self-hosted OpenAI-compatible endpoints).

Use it in a request

Either set the channel as the default for your API key, or override per request with the X-Forge-Channel header.

bashbash
curl https://api.cytokenhub.com/v1/chat/completions \
  -H "Authorization: Bearer $FORGE_KEY" \
  -H "X-Forge-Channel: ch-my-openai-prod" \
  -d '{ "model": "openai/gpt-5", "messages": [...] }'

Supported providers

  • OpenAI (incl. Azure OpenAI)
  • Anthropic
  • Google (Gemini + Vertex AI)
  • AWS Bedrock
  • DeepSeek, Mistral, Together, Groq, Fireworks
  • Any OpenAI-compatible endpoint (Ollama, vLLM, LM Studio…)
BYOK keys are encrypted at rest with per-tenant envelope keys. Forge engineers cannot read them, and they never appear in logs.