Integrations

LLMRPM speaks two wire formats: an OpenAI-compatible API and an Anthropic-compatible API. Any client that lets you set a custom base URL and a bearer key can talk to it. Pick your tool below for a step-by-step recipe.

Supported tools

Each guide covers configuration, a working example, recommended models, and troubleshooting for one tool. Every recipe uses your key from /dashboard/api-keys and one of the two LLMRPM base URLs.

How it works

Every integration configures one of two base URLs with your LLMRPM key. If a tool lets you override the base URL of the OpenAI or Anthropic client it already uses, it works with LLMRPM.

API shapeBase URLUsed by
OpenAI-compatiblehttps://llmrpm.com/api/v1OpenAI SDK, Cursor, Windsurf, Continue, Zed, most tools
Anthropic-compatiblehttps://llmrpm.com/apiAnthropic SDK, Claude Code, Cline (Anthropic mode)
Bearer auth, both formats
LLMRPM authenticates every request with Authorization: Bearer llmrpm_.... For Anthropic SDKs set the authToken field (not apiKey) so the client sends a bearer token instead of an x-api-key header.
Supported surface
LLMRPM exposes chat completions, Anthropic messages, a model list, and usage endpoints. Features that depend on other endpoints — embeddings, image or audio generation, or provider-specific extensions — are not part of this surface, so configure integrations for chat only.

Environment variables

The examples reference a small, consistent set of variables. Set only the ones your integration uses:

VariableValue
LLMRPM_API_KEYYour key from /dashboard/api-keys, e.g. llmrpm_....
LLMRPM_BASE_URLhttps://llmrpm.com/api/v1 — for OpenAI-compatible clients and raw HTTP.
LLMRPM_ANTHROPIC_BASE_URLhttps://llmrpm.com/api — for Anthropic SDKs only; see Messages.
.env
LLMRPM_API_KEY=llmrpm_your_key_here
LLMRPM_BASE_URL=https://llmrpm.com/api/v1
LLMRPM_ANTHROPIC_BASE_URL=https://llmrpm.com/api
One key per environment
Issue separate keys for local, staging, and production from /dashboard/api-keys. Revoking a leaked key then affects only that environment, and per-key usage stays legible in your usage view.

Next steps