LLMAPI · Developer tools

Get the URL right. Connect your client.

Check a base URL, generate settings, and follow your client’s guide. Use it without signing up or entering an API key.

Find your client guideCreate an LLMAPI account

1. Check the base URL

Checks llmapi.pro URL formatting locally in your browser. No API request is made.

Claude Code uses the base URL without /v1; OpenAI-compatible clients use the base URL with /v1.

2. Copy the settings

export ANTHROPIC_BASE_URL="https://llmapi.pro"
export ANTHROPIC_AUTH_TOKEN="YOUR_LLMAPI_KEY"
claude

Replace the key placeholder in your own client. For desktop apps, copy the individual fields and choose a model available to your account. Follow the Cursor guide for its model naming requirements.

Start with your client

Anthropic

Claude Code

https://llmapi.pro

Set the environment variables and launch the client from that terminal.

OpenAI-compatible

Cursor

https://llmapi.pro/v1

Choose the provider type in the guide, then enter your base URL, key and available model.

OpenAI-compatible

Cline

https://llmapi.pro/v1

Choose the provider type in the guide, then enter your base URL, key and available model.

OpenAI-compatible

Roo Code

https://llmapi.pro/v1

Choose the provider type in the guide, then enter your base URL, key and available model.

OpenAI-compatible

Cherry Studio

https://llmapi.pro/v1

Choose the provider type in the guide, then enter your base URL, key and available model.

OpenAI-compatible

Chatbox

https://llmapi.pro/v1

Choose the provider type in the guide, then enter your base URL, key and available model.

Base URL or request endpoint?

Use caseURL to use
Claude Codehttps://llmapi.pro
OpenAI-compatible clienthttps://llmapi.pro/v1
Direct Anthropic HTTP requesthttps://llmapi.pro/v1/messages

A client builds its request path from the protocol settings. A direct HTTP request uses the complete endpoint. Read the HTTP examples

Trouble connecting?

401

Check the service that issued the key and whether the key is active. A correct URL does not validate a credential.

404

Compare the selected protocol and final request path. Check for an extra or missing /v1.

403 / 429

Check account access, quota and concurrency limits. Avoid repeated rapid retries.

5xx

Retain the timestamp and request ID, then retry later or share a redacted error with support.

Full troubleshooting reference →

Ready to connect?

Create an account, choose your billing option in the console, and configure your key. Available models and charges depend on the current product options and your account access.