AI Gateway
Chat Completions
POST
Pass-through to the provider’s chat completions endpoint. Request and response bodies follow the standard OpenAI Chat Completions schema. The gateway infers the provider from the model name; override with
X-Toolken-Provider.
Headers
Your Toolken API key. Validated by the gateway and stripped before forwarding.
Your provider key in Bearer format (BYOK), e.g.
Bearer sk-.... Forwarded untouched, never stored.Primary attribution channel. JSON object of key-value pairs (e.g.
{"agent":"research-agent","customer_id":"cust_abc"}). Each key becomes a groupable dimension in the dashboard.Flat-header shorthand.
X-Toolken-Metadata-Agent: research-agent writes metadata key agent. Equivalent to sending the same key in X-Toolken-Metadata.Sets the
feature metadata key. Use to group costs by agent name, workflow, UI surface, or job type.Sets the
customer_id metadata key. Use to attribute costs to an end-customer, org slug, or account ID.Body
Model identifier (e.g.
gpt-4o).Conversation messages, following the standard OpenAI messages schema.
If true, the gateway streams Server-Sent Events back from the provider.
Maximum tokens to generate. Capped per workspace.
Sampling temperature. Forwarded verbatim.
Response
Unique completion ID.
Always
chat.completion.The model that produced the response.
The generated choices, each with
message and finish_reason.Token counts:
prompt_tokens, completion_tokens, total_tokens.