Migrate

Migrate from the Anthropic API

Messages-API compatible. Point the Anthropic SDK (or Claude Code) at idapt with one base URL.

Change the base URL

- https://api.anthropic.com
+ https://idapt.app/api/anthropic/v1

Claude Code: export ANTHROPIC_BASE_URL=https://idapt.app/api/anthropic/v1 and ANTHROPIC_API_KEY=<your uk_ key>.

What moves

Anthropic API	In idapt	How
POST /v1/messages (stream, tools, system)	Identical Messages endpointTool_use/tool_calls and SSE shapes translate 1:1.	Automatic
GET /v1/models	Model list + detail	Automatic
Claude Code	Works via ANTHROPIC_BASE_URL; billing runs through your idapt included usage or credit balance	Automatic
Batches / Files / Admin APIs	Not on the compat surface	No equivalent

How to migrate

1
Create an idapt API key
Settings → Gateway → API keys. Scoped keys with optional USD spend caps.
2
Point the SDK (or Claude Code) at idapt
Set the base URL to https://idapt.app/api/anthropic/v1 and use your uk_ key as the API key. Claude Code needs just the two env vars.
3
Route your way
Requests route to Claude models via the cheapest live path (Anthropic-native or aggregated). Add your own Anthropic key to pin billing to your account.

Or run the models on your own computer

Private AI runs open models (Llama, Qwen, Gemma, Mistral, Phi and more) on hardware you own, through the idapt daemon: free, never rate-limited, and no third-party AI provider ever sees the prompt. They sit beside the 200+ cloud models in the same chat.

FAQ

Does Claude Code really work?

Yes. Claude Code honors ANTHROPIC_BASE_URL, so it runs against idapt unchanged: same models, streaming, and tool calls, with idapt-side usage tracking and spend caps.

Which endpoints exist?

The Messages API and model listing, the shapes coding tools and SDK chat apps use. Batches/Files/Admin surfaces aren't proxied.

Go deeper

Create an API key