Skip to main content

Overview

Planck AI Gateway is the public entry point for AI requests. Use one base URL:
The gateway exposes explicit, supported routes instead of an unrestricted generic proxy. This keeps billing, logging, routing, provider-key handling, and safety features consistent across requests.

Supported Public Routes

Basic OpenAI-Compatible Request

BYOK Provider Keys

When you use your own provider key, Planck still needs a Planck API key for authentication. Send the provider key separately:
You can also put the Planck key in Planck-Auth and keep the provider key in Authorization:

Custom And Self-Hosted Targets

Custom targets are for OpenAI-compatible endpoints that you run or have approved for your organization. They are not a generic public proxy. Custom targets are:
  • BYOK-only
  • limited to supported operations such as chat, responses, and embeddings
  • configured per organization before production use
  • required to use https for external targets
  • blocked from private-network destinations outside local development
Send the target base URL with Planck-Target-URL:
For local development, localhost-style targets can be enabled by the gateway operator. This is intended for local testing only.

Anthropic

For most applications, use the mapped Anthropic route:
For Anthropic-native requests that need Anthropic-specific paths or semantics, use: