Integrations / Use /v1 for OpenAI-compatible setups / Model IDs
Developer Tools

Use CheapAI in the tools you already have.

The cleanest path is to treat CheapAI as an OpenAI-compatible provider. Some tools are already reflected in the current repo examples, while others are best described as compatible when they expose the same settings.

Support levels by tool type

Tool or categoryStatusBase URLNotes
Direct API calls, curl, Python, Node.js Tested https://cheapai-netifly-app.up.railway.app/v1 This is the reference path used across the current repo examples.
Claude Code Supported /v1 Use the dedicated guide and the current public env-var pattern shown there.
ChatBox Compatible /v1 Field names vary by version, but the provider values stay the same.
LangChain, n8n, automation tools Compatible /v1 Works when the tool accepts a custom OpenAI-style base URL.
Cline, Roo, Kiro, similar editor agents Depends on tool /v1 Usually workable when a custom OpenAI provider is exposed, but feature depth depends on the client.

Coding tools and editor agents

For Claude Code, Cursor-style clients, and similar coding tools, the safe default is to configure CheapAI as a custom provider using your delivered key and the /v1 base URL.

  • Start with one model slug instead of trying a full list on day one.
  • Use smaller or cheaper models for iteration, then switch to heavier models when the task demands it.
  • Store secrets in local environment variables or the app's own secret settings, not in repo files.

Chat and UI tools

Chat clients typically ask for four things: provider type, base URL, API key, and model. If the app supports a custom OpenAI-compatible provider, CheapAI usually fits cleanly.

ChatBox

Use the ChatBox guide for desktop and mobile setup patterns, plus the field names that usually matter.

Open ChatBox guide

Other chat apps

If the app can target a custom OpenAI-style base URL and lets you choose the model ID, start with the same values.

Automation and framework setups

Workflow tools and orchestration libraries usually succeed when they rely on standard OpenAI-compatible chat completions and let you override the base URL. This covers many common backend, script, and agent workflows.

Environment template
CHEAPAI_BASE_URL=https://cheapai-netifly-app.up.railway.app/v1
CHEAPAI_API_KEY=YOUR_CHEAPAI_API_KEY
CHEAPAI_MODEL=claude-sonnet-4-6-20260217

Base URL rule of thumb

Use the root host as the canonical public host in documentation and debugging. Use https://cheapai-netifly-app.up.railway.app/v1 when a client expects the OpenAI-compatible base URL itself. If your delivery package specifies a tool-specific variant, follow that exact package for that order.

Browse docs
On this page