Getting Started

Tool Integrations

Most setup issues come from one mismatch: the tool expects one provider format, but the API key was created from a group meant for another one. This page keeps that mapping explicit.

Recommended Mode by Tool

Match the tool to the request format it actually exposes, not just the model family you want to reach.

ToolRecommended modeWhy
CursorOpenAI-compatibleCursor config is centered on OpenAI-style provider settings.
CodexOpenAI-compatibleCodex uses the OpenAI-compatible route today.
ClineOpenAI-compatibleCline's third-party provider flow is typically OpenAI-compatible.
Claude CodeAnthropic-nativeBest fit for Anthropic-native request behavior and cache controls.
OpenCodeDepends on provider adapterOpenCode can use either path if the configured adapter matches the key's group.
Do not assume a model family alone determines the right setup. The tool's request format is what matters first.

Mainstream Coding Tools

These cards summarize the minimum configuration and the operational caveat for each supported tool family.

Cursor

Use the OpenAI-compatible path in Cursor Models settings.

Create a key from an OpenAI-compatible group.
Set Override OpenAI Base URL to https://api.lingcorex.ai/v1.
Add only the exact model IDs enabled for your account.

Codex

Use OPENAI_BASE_URL and OPENAI_API_KEY, or a persistent config.toml plus auth.json setup.

Create a key from an OpenAI-compatible group.
Use https://api.lingcorex.ai/v1 as the base URL.
Remember that Anthropic explicit cache_control fields are not exposed through this request shape.

Cline

Treat Cline as an OpenAI-compatible tool in this documentation set.

Choose the custom OpenAI or openai-compatible provider path.
Set the base URL to https://api.lingcorex.ai/v1.
Use a model that belongs to the key's group.

Claude Code

Use an Anthropic-native key and the Anthropic-native base URL.

Set ANTHROPIC_BASE_URL=https://api.lingcorex.ai.
Create the key from an Anthropic-native group.
This is the better fit when explicit cache behavior matters.

OpenCode

OpenCode can work through either route if the adapter and the key group match.

Use an OpenAI-compatible key with an OpenAI-compatible adapter.
Use an Anthropic-native key with an Anthropic-native adapter.
Do not mix the provider adapter and the group's endpoint family.

Minimal Config Examples

Use these snippets as the shortest stable starting point before you add project-specific defaults.

Codex environment variables
export OPENAI_BASE_URL=https://api.lingcorex.ai/v1
export OPENAI_API_KEY=YOUR_API_KEY
codex
Claude Code environment variables
export ANTHROPIC_BASE_URL=https://api.lingcorex.ai
export ANTHROPIC_API_KEY=YOUR_API_KEY
claude
OpenCode (OpenAI-compatible adapter)
{
  "provider": {
    "lingcorex": {
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "baseURL": "https://api.lingcorex.ai/v1",
        "apiKey": "YOUR_API_KEY"
      }
    }
  }
}

Tool Setup Screenshots

Add real setup screenshots later for the tooling pages that benefit from a guided UI walkthrough.

Cline provider settings configured with LingCoreX base URL and OpenAI-compatible API key fields.

Cline provider settings

Shows where to set the provider type, base URL, API key, and model ID when connecting Cline through LingCoreX.

Claude Code environment setup screenshot for LingCoreX Anthropic-compatible configuration.

Claude Code environment setup

Highlights the environment values used by Claude Code when routing Anthropic-native requests through LingCoreX.

The Cursor Models screenshot is still pending; the Cline and Claude Code setup screenshots below show the current integration paths.

Need current pricing or the product overview?

Use pricing for the public commercial view, or return to the landing page for the high-level product story.