Docs / Setup Guide

Setup Guide: protocol / Base URL / key

Three protocols, three Base URLs

llmapi provides Anthropic, OpenAI and Gemini compatible endpoints. The protocol determines how your client sends requests; available models and billing also depend on your key and channel.

Anthropic
https://llmapi.pro — path /v1/messages, header x-api-key. Used by Claude Code and the Anthropic SDK. Base URL has no /v1
OpenAI
https://llmapi.pro/v1 — path /v1/chat/completions, header Authorization: Bearer. Used by most third-party clients. Base URL includes /v1
Gemini
https://llmapi.pro — path /v1beta/models/{model}:generateContent, auth via x-goog-api-key or ?key=. Used by the Google GenAI SDK. SDK base has no /v1beta (the SDK appends it)
Most common gotcha: a missing or extra /v1 causes 404. Claude Code (Anthropic): no /v1; OpenAI-compatible clients: with /v1; Gemini SDK base: no /v1beta (the SDK appends it).

API Key

A monthly subscription uses a subscription key, with supported models sharing the plan quota. Pay-as-you-go API billing uses a separate key and balance. Select the matching key type in the Console, then configure your client protocol. Topping up API credit does not increase subscription quota.

Never publish your key or commit it to a repository.

Model names

Copy the exact model ID from the subscription model list or pay-as-you-go channels, and check that your client protocol supports it. The model catalogue labels each model’s billing mode.

Need help? Email support@llmapi.pro · Home