BETA

Docs

Integration guides

Step-by-step setup for Claude Code, Cursor, Codex CLI, and the other clients Apily already documents.

Anthropic MessagesClaude CodeAnthropic's CLI agent. Apily serves a native Anthropic Messages endpoint, so Claude Code connects directly — no compatibility shim needed.Instructions OpenAI ResponsesCodex CLIOpenAI's CLI agent. Uses its own ~/.codex/config.toml with a custom model_provider.Instructions OpenAI-compatibleOpenCodeOpen-source terminal agent. The provider is declared in opencode.json via @ai-sdk/openai-compatible.Instructions OpenAI-compatibleCursorVS Code-based IDE. Its model settings allow overriding the OpenAI base URL.Instructions OpenAI-compatibleClineVS Code extension. Its "OpenAI Compatible" provider accepts an arbitrary base URL and model ID.Instructions OpenAI-compatibleKilo CodeVS Code extension with an agent mode. Configured as an OpenAI-compatible provider.Instructions OpenAI-compatibleCherry StudioDesktop chat client for Windows, macOS and Linux. Added as a custom OpenAI-type provider; the API address is entered with a trailing slash.Instructions OpenAI-compatibleDeepSeek HarnessDeepSeek's official agent harness with a web UI. A third-party gateway is declared as a custom provider: id, address, protocol and model list.Instructions OpenAI-compatibleHermesNous Research's agent with a desktop UI and a CLI. Your own address is added in the settings as a custom endpoint.Instructions OpenAI-compatiblePiA minimal terminal harness. Custom providers and models are declared in ~/.pi/agent/models.json.Instructions OpenAI-compatibleOpenClawSelf-hosted agent. Works with any OpenAI-compatible endpoint.Instructions