OpenAI · Anthropic · Claude Code

One Base URLfor every AI model

Point the Anthropic SDK, OpenAI SDK, Claude Code, or curl at a single endpoint — no code changes, live in minutes.

Get started Check your key

$ export ANTHROPIC_BASE_URL=https://api.laalaa.me

POST api.laalaa.me/v1/chat/completionsdone

$curl-sNhttps://api.laalaa.me/v1/chat/completions

-H "Authorization: Bearer sk-laalaa-••••••••••••"

-d '{"model": "claude-opus-4-8", "stream": true}'

→request sent · bearer accepted · key → bound server

✓routed · anthropic

← 200 OK·ttfb384ms·text/event-stream

Same code. Every model. One Base URL.

modelclaude-opus-4-8gpt-5.5claude-sonnet-5qwen-3.8-flashglm-5.3-flash

enabled models

live from your upstream servers

setup guides

verified against real config screens

wire protocols

OpenAI-shaped and Anthropic-shaped

pricing tiers

all models on every tier

Integrations

Works with the tools you already use

Bring every SDK and AI tool into one seamless gateway.

Your Application

SDK • API • AI Tools

Laalaa

Gateway

Operational

API Key Routing

Server Options

Server Option 01

Claude

Online

Key A

Server Option 02

OpenAI

Online

Key B

Your Application

SDK • API • AI Tools

Laalaa

Gateway

Operational

API Key Routing

Server Option 01

ClaudeOnline

Other server options available · Server Option 02 · OpenAI

Claude CodeCodexClineKilo CodeHermesCursorOpenAI SDKAnthropic SDK

Dedicated routing, automatic failover

Each API key stays on its assigned server for predictable performance and isolation. If a primary upstream inside that server fails, the request shifts to its configured backup — never another server.

Integrations

Works across your AI stack

Connect leading AI providers, coding tools, and SDKs through one gateway.

AI Providers

OpenAI
Anthropic
Claude
Gemini
Google
DeepSeek
Qwen
Alibaba Cloud
Meta
Azure
NVIDIA
xAI
Mistral AI
Cohere
Groq
Perplexity
Together AI
Fireworks AI
Hugging Face
IBM
Bedrock
AWS
ByteDance
Z.ai / GLM
MiniMax
Moonshot

Developer Tools

Claude Code
Codex
Cursor
Cline
Kilo Code
Hermes
Continue
Roo Code
Windsurf
OpenAI SDK
Anthropic SDK

Provider support is at the protocol level — which models are reachable depends on the servers your key is assigned to.

Why a gateway

Why Laalaa Gateway

What you get on top of being able to call the model.

Works with OpenAI and Anthropic

One endpoint speaks both /v1/chat/completions and /v1/messages — no juggling formats.

Just change the Base URL

Keep your code as-is; swap the base URL and you switch providers in seconds.

Secured by your own key

Accepts a Bearer token or x-api-key, then normalizes it safely before forwarding.

Instant streaming over SSE

Tokens arrive one by one with no buffering — as fast as the native API.

Migration

Swap the base URL, keep everything else

No new deployment, no new code — same SDKs, same key shape, same model ids.

shell — 1 line changed

export ANTHROPIC_AUTH_TOKEN="sk-xxxxxxxxxxxx"

ANTHROPIC_BASE_URL="https://api.anthropic.com"

ANTHROPIC_BASE_URL="https://api.laalaa.me"

connected42 modelssame SDKsame key shape

One endpoint, two wire protocols

The gateway speaks both the OpenAI and the Anthropic shape on the same host.

POSThttps://api.laalaa.me/v1/chat/completionsOpenAI-shaped
POSThttps://api.laalaa.me/v1/messagesAnthropic-shaped
GEThttps://api.laalaa.me/v1/modelsOpenAI-shaped

Authenticated with Authorization: Bearer or x-api-key — the gateway normalizes both before forwarding.

1curl https://api.laalaa.me/v1/chat/completions \2  -H "Authorization: Bearer sk-xxxxxxxxxxxx" \3  -H "Content-Type: application/json" \4  -d '{5    "model": "claude-opus-4-8",6    "stream": true,7    "messages": [{"role": "user", "content": "Hello"}]8  }'

Three steps to working

No new deployment, no new code — swap the base URL and you're done.

Get a key

Buy via the Telegram bot or a vendor — your key starts with sk-.

Point your tool

Set the base URL in the SDK or tool you already use.

Call any model

Use real model ids — the gateway handles routing and streaming.

Reliability

What happens when an upstream fails

The breaker counts only eligible failures and falls through to the endpoint's configured chain — never a global search for any free server.

Circuit breaker & failover

closed

Primary endpoint

priority 1

200 · serving

no traffic

Configured fallback

fallbackIds[0]

standby

consecutive eligible failures0/5

routing Circuit CLOSED — the primary endpoint is serving normally.

400/404/413 never count — only connect/timeout/429/5xx. Cooldown 30s. Fallback happens only before the first response byte, so a stream that already started is never silently restarted.

Integrations