Skip to main content

Overview

TokenLab works with the official OpenAI SDKs by pointing the client to https://api.tokenlab.sh/v1. For most new projects, prefer Chat Completions as the default OpenAI-compatible path. Use Responses API only when you explicitly need Responses-specific behavior. Responses-specific fields are not guaranteed to behave identically across every model and routed path.
Python, JavaScript, and Go have official OpenAI SDKs. PHP works well with OpenAI-compatible community clients, but it is not an official OpenAI SDK.
Type: Native SDKPrimary Path: OpenAI-compatible / Chat CompletionsSupport Confidence: Supported core path

Installation

Use POST /v1/responses only when you explicitly need Responses-specific behavior. Some Responses-only fields can still depend on the selected model and routed path.

Configure the Client

Advanced: Responses API

Use this path only when your tool or workflow explicitly depends on OpenAI Responses semantics.

Streaming with Responses

Tools / Function Calling

Vision with Responses

Embeddings

Chat Completions

Chat Completions is the default OpenAI-compatible path for TokenLab:

Troubleshooting

  • Verify the base URL is exactly https://api.tokenlab.sh/v1
  • Check for proxy interference or custom HTTP client overrides
  • Make sure your SDK version is current before debugging provider behavior
  • Check that your API key starts with sk-
  • Verify the key is active in TokenLab dashboard
  • Confirm the SDK is sending Authorization: Bearer ...
  • responses.create(...) sends requests to /v1/responses
  • chat.completions.create(...) sends requests to /v1/chat/completions
  • Use Chat Completions by default unless you explicitly need Responses-specific behavior