Personal API keys

A personal API key lets you reach your workspace’s models from outside Langdock, so you can use them in coding tools like Claude Code or Codex, or in a project of your own. The key authenticates as you, which means it spends your usage budget and reaches the completion endpoints only.

API keys section in account settings showing the extra usage budget and when it resets

Your admin has to give you access before API keys appears in your account settings, and you need usage budget to spend. On Langdock Cloud that means extra usage is enabled and your effective extra usage limit is above zero. On BYOK and dedicated deployments it means your admin set an individual extra usage limit above zero, where plan and group limits don’t apply to personal keys and extra usage doesn’t have to be enabled. Whatever you spend through the key comes out of the same budget as your chat and agent usage. On trial workspaces you can only create a key once API keys have been enabled for the trial.

Create a personal API key

Open API keys

Go to Settings > Account > API keys.

Enter the key details

Your API keys section with the Create API key button

Click Create API key. Give the key a name that tells you where it’s used, so you know which tool to update later, and choose when it expires.

Create and copy the key

Create a new API key dialog with fields for name and expiry and a summary of what the key can do

Click Create API key, then copy the key and store it somewhere safe. Langdock shows it once and never again.

Never share a personal API key. It authenticates as you and spends your budget, so anyone who has it is working as you. Use a workspace API key for shared applications and automations, and see API key best practices for storing keys safely.

The page also tracks how much of your budget you have used and when it resets. If there is nothing left to spend, you can request a higher limit right there when usage requests are enabled, or ask your workspace admin.

Connect a tool

Connect your tools walks you through the setup for Claude Code, Claude Desktop, OpenCode, Codex, and direct API calls with cURL. You can also connect Cursor with the same key. Pick an available model and the examples update to match, then follow the steps for your tool. The guides below match that setup. Replace YOUR_API_KEY with your key and your-model-id with an ID from Available models. Use eu or us to match your workspace’s model region, or copy the exact base URL from Connect your tools. On dedicated deployments the base URL starts with your deployment origin instead of https://api.langdock.com.

Claude Code uses the Anthropic Messages API through Langdock.

Check available Claude models

curl https://api.langdock.com/anthropic/eu/v1/models \
  -H "Authorization: Bearer YOUR_API_KEY"

Add your settings

Add this to ~/.claude/settings.json (on Windows: %USERPROFILE%\.claude\settings.json), and create the file if it does not exist. Replace the model IDs with ones from the previous step, and make sure ANTHROPIC_API_KEY is not set:

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.langdock.com/anthropic/eu",
    "ANTHROPIC_AUTH_TOKEN": "YOUR_API_KEY",
    "ANTHROPIC_MODEL": "your-model-id",
    "ANTHROPIC_SMALL_FAST_MODEL": "your-model-id"
  }
}

Start Claude Code

claude

Claude Code speaks the Anthropic Messages API, which Langdock serves at the base URL above. All requests are now routed through your workspace.

Claude Desktop can run chats on Langdock models through third-party inference.

Enable Developer Mode

In Claude Desktop, open Help → Troubleshooting → Enable Developer Mode.

Configure the gateway

Open Developer → Configure third-party inference. Set Inference provider to Gateway. Under Gateway credentials, enter:

Gateway base URL:    https://api.langdock.com/anthropic/eu
Gateway API key:     YOUR_API_KEY
Gateway auth scheme: bearer
Credential kind:     Static API key

Test and apply

Keep Model discovery enabled, then click Test connection and Test model discovery. Claude discovers the Anthropic models available in your workspace. Click Save Changes, then Apply Changes. Claude relaunches; select Continue with Gateway if prompted.

Cursor has no built-in card under Connect your tools yet. Point its OpenAI provider at Langdock:

Open model settings

In Cursor, open Cursor Settings > Models.

Add your key and base URL

Paste your personal API key into the OpenAI provider field and click Save. Turn on Override OpenAI Base URL and enter this URL with /v1 and no trailing slash:

https://api.langdock.com/openai/eu/v1

Add a workspace model

Enter the exact ID of a model from Available models, then click Add Custom Model. Select that model for chat.

Custom API keys in Cursor cover chat models only. Tab completion keeps using Cursor’s built-in models. Agent mode fails with an HTTP 400 error, because Langdock’s Chat Completions endpoint accepts only tools of type function. For agentic coding, use Claude Code, Codex, or OpenCode instead.

Codex uses Langdock’s OpenAI Responses endpoint (wire_api = "responses").

Add your config

Add this to ~/.codex/config.toml (on Windows: %USERPROFILE%\.codex\config.toml), and create the file if it does not exist:

model = "your-model-id"
model_provider = "workspace"

[model_providers.workspace]
name = "Langdock"
base_url = "https://api.langdock.com/openai/eu/v1"
wire_api = "responses"
experimental_bearer_token = "YOUR_API_KEY"

Start Codex

codex

Or open the Codex / ChatGPT desktop app. This file stores your key on this computer. If you share the machine, revoke the key in Langdock and create a new one.

OpenCode uses the Anthropic-compatible endpoint through Langdock.

Add your config

Add this to opencode.json in your project, or to ~/.config/opencode/opencode.json (on Windows: %USERPROFILE%\.config\opencode\opencode.json). You can list more workspace models under models:

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "workspace": {
      "npm": "@ai-sdk/anthropic",
      "name": "Langdock",
      "options": {
        "baseURL": "https://api.langdock.com/anthropic/eu/v1"
      },
      "models": {
        "your-model-id": { "name": "Your model" }
      }
    }
  }
}

Start OpenCode and connect

opencode

Run /connect, select Other, enter workspace as the provider ID, then paste your API key.

Choose the model

Choose the model with /models, or start OpenCode with it directly:

opencode --model workspace/your-model-id

Call the completion APIs directly from your own projects.

List available models

curl https://api.langdock.com/openai/eu/v1/models \
  -H "Authorization: Bearer YOUR_API_KEY"

Send a Chat Completions request

curl https://api.langdock.com/openai/eu/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "your-model-id", "messages": [{"role": "user", "content": "Hello"}]}'

Or use the Anthropic-compatible API

curl https://api.langdock.com/anthropic/eu/v1/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "your-model-id", "max_tokens": 1024, "messages": [{"role": "user", "content": "Hello"}]}'

Use any OpenAI- or Anthropic-compatible SDK by pointing its base URL at the URLs above. See the Chat Completions, Responses, and Anthropic Messages API docs for full request shapes.

Your key works with the OpenAI compatible Chat Completions and Responses APIs, the Anthropic Messages API, the Google Completion API, and the Mistral Completion API. Which of them you can call depends on the models configured for your workspace. Available models shows what you can pick for the built-in OpenAI and Anthropic guides, and for Google and Mistral you follow the API documentation instead. Personal keys stop at the completion endpoints. The Agent, Embedding, Knowledge Folder, Integrations, Skills, Usage Export, and Audit Logs APIs need a workspace API key with the matching scope.

Rotate or revoke a key

Open the menu next to a key under Your API keys:

Rotate key replaces the secret. The old one stops working immediately, so update every connected tool with the new key.
Revoke key switches the key off for good.

Your workspace admin can revoke your keys as well. They also stop working if your admin takes away your access to personal API keys or deactivates your workspace membership.

Get Started

Chat

Skills

Library

Agents

Workflows

Integrations

Microsoft Plugins

Models & Limits

Guides

Account

Resources

Troubleshooting

Personal API keys

Create a personal API key

Connect a tool

Rotate or revoke a key

​Create a personal API key

​Connect a tool

​Rotate or revoke a key

Create a personal API key

Connect a tool

Rotate or revoke a key