> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.beatapi.io/integrations/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server. # Integrations > Point an existing coding agent, desktop chat client, or LLM platform at BeatAPI by changing one base URL and one API key. # Integrations Most tools that already speak to a model vendor can speak to BeatAPI instead. Nothing is rewritten — you change a base URL, paste a BeatAPI key, and pick a model ID. BeatAPI answers on four request formats, so a tool keeps using whichever one it was built for. | Format | Endpoint | Tools that use it | | ----------------------- | -------------------------------------- | ----------------------------------------------------------------------------- | | OpenAI Chat Completions | `POST /v1/chat/completions` | Cherry Studio, ChatBox, Cline, Cursor, AnythingLLM, Dify, Immersive Translate | | OpenAI Responses | `POST /v1/responses` | Codex CLI | | Anthropic Messages | `POST /v1/messages` | Claude Code | | Gemini-compatible | `POST /v1beta/models/{model}:{action}` | Gemini SDK integrations | ## AI coding tools #### [Claude Code](/integrations/claude-code) Terminal coding agent, configured through `ANTHROPIC_BASE_URL`. #### [Codex CLI](/integrations/codex-cli) Add BeatAPI as a custom model provider in `config.toml`. #### [Gemini CLI](/integrations/gemini-cli) Two environment variables point it at the native Gemini endpoint. #### [Cline](/integrations/cline) The VS Code extension, using its OpenAI Compatible provider. #### [Cursor](/integrations/cursor) Override the OpenAI base URL in the editor's model settings. #### [CC-Switch](/integrations/cc-switch) Manage Claude Code and Codex CLI providers from one desktop app. ## Chat clients #### [Cherry Studio](/integrations/cherry-studio) Add BeatAPI as an OpenAI-type provider and load the model list. #### [ChatBox](/integrations/chatbox) Works through the OpenAI, Claude, or Gemini provider types. #### [AnythingLLM](/integrations/anythingllm) Use BeatAPI as the chat model behind a local knowledge base. ## Platforms #### [n8n](/integrations/n8n) Use built-in model and HTTP nodes with task-specific workflow exports. #### [Dify](/integrations/dify) Configure text models; use the separately versioned tool plugin for actions. #### [Zapier](/integrations/zapier) Use the public model, Social Data, capability, and media actions. #### [Make](/integrations/make) Start from a shareable media template or build an HTTP scenario. #### [Immersive Translate](/integrations/immersive-translate) Add BeatAPI as a custom translation service in the browser extension. ## What every guide has in common Three values are the same everywhere, so if a tool is not listed above, try its OpenAI-compatible option with these: | Setting | Value | | -------- | ------------------------------------------------------------------------------------------------------------ | | Base URL | `https://api.beatapi.io/v1` for OpenAI-compatible tools, `https://api.beatapi.io` for Anthropic-native tools | | API key | A key created in [Dashboard → API Keys](https://beatapi.io/dashboard/apikeys) | | Model ID | Any ID from [`GET /v1/models`](/text-api) or the [pricing page](https://beatapi.io/pricing) | > **Note** > > The base URL is the only place the `/v1` suffix is ambiguous. Tools that follow the OpenAI SDK convention want `https://api.beatapi.io/v1`; tools built on the Anthropic SDK want `https://api.beatapi.io` and add `/v1/messages` themselves. Each guide states which one applies. ## Choosing a model Every integration reaches the same catalogue with the same key. These are reasonable starting points; the [Text API](/text-api) pages list each family in full. | Need | Model ID | | --------------------- | ---------------------------------------------------------------- | | Agentic coding | `claude-fable-5-1`, `gpt-5.6-sol` | | Hard reasoning | `claude-opus-5`, `gpt-6-astra`, `deepseek-v4-pro-0813` | | Everyday chat | `claude-sonnet-5`, `gpt-5.6-terra`, `glm-5.3` | | High volume, low cost | `claude-haiku-4-5-20251001`, `gemini-3.7-flash`, `glm-5.3-flash` | | Long context | `minimax-m3`, `grok-4.7` | ## Keeping keys safe * Create a separate key per tool so one can be revoked without disturbing the others. * Prefer an environment variable over a value pasted into a config file that may be committed. * Add config files that hold a key to `.gitignore`. * Watch spend per key under `by_api_key` in [`GET /v1/usage`](/quick-guide) or on the dashboard. > Point an existing coding agent, desktop chat client, or LLM platform at BeatAPI by changing one base URL and one API key. ## Docs - [Using BeatAPI in Claude Code](https://docs.beatapi.io/integrations/claude-code.md): Configure Claude Code to send its requests to BeatAPI, so one key reaches every Claude model on the account. - [Using BeatAPI in Codex CLI](https://docs.beatapi.io/integrations/codex-cli.md): Add BeatAPI as a custom model provider in Codex CLI so the terminal coding agent runs on any model in your account. - [Using BeatAPI in Gemini CLI](https://docs.beatapi.io/integrations/gemini-cli.md): Point Gemini CLI at BeatAPI with two environment variables and run the Gemini models on your BeatAPI balance. - [Using BeatAPI in Cline](https://docs.beatapi.io/integrations/cline.md): Configure the Cline extension for VS Code to run on BeatAPI through its OpenAI Compatible provider. - [Using BeatAPI in Cursor](https://docs.beatapi.io/integrations/cursor.md): Configure BeatAPI as a custom model provider for supported Cursor chat requests, with clear limits for Cursor Tab. - [Using BeatAPI in CC-Switch](https://docs.beatapi.io/integrations/cc-switch.md): Manage the BeatAPI provider for Claude Code and Codex CLI from one desktop app and switch between providers without editing config files. - [Using BeatAPI in Cherry Studio](https://docs.beatapi.io/integrations/cherry-studio.md): Add BeatAPI as an OpenAI-type provider in Cherry Studio and chat with every model on the account from one desktop app. - [Using BeatAPI in ChatBox](https://docs.beatapi.io/integrations/chatbox.md): Configure ChatBox against BeatAPI through its OpenAI, Claude, or Gemini provider type. - [Using BeatAPI in AnythingLLM](https://docs.beatapi.io/integrations/anythingllm.md): Use BeatAPI as the chat model behind an AnythingLLM workspace and keep documents and embeddings local. - [Using BeatAPI in n8n](https://docs.beatapi.io/integrations/n8n.md): Connect BeatAPI models and data to n8n, then import a task-specific workflow with clear validation boundaries. - [Using BeatAPI in Dify](https://docs.beatapi.io/integrations/dify.md): Configure BeatAPI as a model provider in Dify and use it across apps, agents, and workflows. - [Using BeatAPI in Zapier](https://docs.beatapi.io/integrations/zapier.md): Connect the public BeatAPI Zapier app and understand which actions are available today. - [Using BeatAPI in Make](https://docs.beatapi.io/integrations/make.md): Start with a shareable BeatAPI music-video template or create an HTTP scenario for another capability. - [Using BeatAPI in Immersive Translate](https://docs.beatapi.io/integrations/immersive-translate.md): Add BeatAPI as a custom translation service in the Immersive Translate browser extension for bilingual pages, PDFs, and subtitles.