I get 401
I get 401
Your
X-Toolken-Key is missing or invalid. Check that the header is present on every request and that the key value is correct.I get 422
I get 422
Your
X-Toolken-Metadata contains an invalid key or exceeds the size or key-count limit. Keys must be lowercase, start with a letter, and use snake_case. Note: malformed JSON is silently ignored, so verify your JSON is well-formed before checking key names.I get 429
I get 429
You hit a request rate limit or the concurrent-stream limit. Read the
Retry-After header and back off before retrying.My requests do not show up in the dashboard
My requests do not show up in the dashboard
Confirm your base URL ends in
/v1, the X-Toolken-Key header is present, and the model name routes to a recognized provider. If the model name is ambiguous, set the X-Toolken-Provider header explicitly.Ruby (ruby-openai) returns 401 from OpenAI
Ruby (ruby-openai) returns 401 from OpenAI
Use
uri_base: "https://gateway.toolken.ai/v1/" (with the trailing slash) and pass Toolken headers via extra_headers. The base_url and default_headers options are not honored by ruby-openai.Go (openai-go) returns 404
Go (openai-go) returns 404
Point a raw
net/http request at https://gateway.toolken.ai/v1/chat/completions with the headers set directly, or verify that your configured base URL preserves the /v1/ path segment.Anthropic requests fail
Anthropic requests fail
The Anthropic SDK base URL is
https://gateway.toolken.ai with no /v1. The SDK appends /v1/messages itself, so adding /v1 to the base URL produces a doubled path and fails.