Docs / OpenAI-compatible

Chat-completions HTTP API — Introduction

The TokenSaver pipeline is exposed under a dedicated prefix on the public API host. Use your TokenSaver API key (ts_…) only—never the LLM vendor key alone for authentication on this surface.

Production base URL

Configure clients with no trailing slash:

https://api.tokensaver.fr/openai/v1

The SDK and console use the native prefix https://api.tokensaver.fr/api/v1 (e.g. POST /pipelines/run). The OpenAI-shaped routes live under /openai/v1 on the same host, in addition—not instead—of /api/v1.

Endpoints

Each route uses the same base URL prefix (no trailing slash).

POST/openai/v1/chat/completions

Chat, tools, stream (SSE)

POST/openai/v1/responses

Responses API shape, same pipeline + extensions

GET/openai/v1/models

List provider/model_id ids

POST/openai/v1/embeddings

Embeddings gateway (no full LLM pipeline)

OpenAPI

Machine-readable contract (filter paths starting with /openai/v1):

GET https://api.tokensaver.fr/api/v1/openapi.json

Next: All request & response headers, Chat completions, or Native pipeline for the same fields in POST /api/v1/pipelines/run.