Skip to main content

​
Short answer

Do not choose only by model name. First confirm which protocol and Key group your tool needs. Then choose by task type, quality, speed, context length, and cost. If you use LLMEasy, Claude Code should usually use the Claude group. Codex CLI, Cursor, Cline, OpenCode, OpenClaw, and other external tools should usually use the GPT group. Copy the Model ID from the model plaza.

​
When you need this

  • You are not sure whether to use the Claude group or the GPT group
  • You switch between Claude Code, Codex CLI, Cursor, Cline, or similar tools
  • A model works, but it is too expensive, too slow, or has too little context
  • You want a cheaper model for batch tasks
  • You want to connect the same API gateway to several AI coding tools

​
Start with the tool, then choose the model

The first step is not comparing model rankings. The first step is checking which protocol the client expects.
Use caseRecommended Key groupCommon Base URL
Claude CodeClaude grouphttps://www.llmeasy.ru
Claude Desktop GatewayClaude group, or the group required by the local gatewayFollow the gateway configuration
Codex CLIGPT grouphttps://www.llmeasy.ru/v1
CursorGPT grouphttps://www.llmeasy.ru/v1
ClineGPT grouphttps://www.llmeasy.ru/v1
OpenCode / OpenClawGPT grouphttps://www.llmeasy.ru/v1
If the protocol or Key group is wrong, the model can still exist but the request may fail with model not found, authentication errors, or an invalid request format.

​
Choose by task type

Task typePrioritize
Complex coding, architecture, long-running tasksReasoning quality, context window, tool-call stability
Daily Q&A and light generationSpeed and cost
Batch translation, classification, summariesUnit price, throughput, stability
Code review and technical documentationCode understanding, long context, stable output
Exploratory tasksStart with a mid-cost model, then switch to a stronger model for critical steps
Do not send every task to the most expensive model by default. Many batch tasks do not need deep reasoning or high creativity. They are often better suited to faster and cheaper models.
  1. Confirm whether the tool supports an OpenAI-compatible or Anthropic-compatible API.
  2. Choose the Claude group or GPT group based on the tool.
  3. Copy the current Model ID from the model plaza.
  4. Test quality, speed, and cost with a small task.
  5. Check usage in the dashboard before using that model long term.
  6. Keep a stronger backup model for complex tasks instead of configuring only one model.

​
Common mistakes

  • Looking only at the display name and not confirming the Model ID.
  • Using a Claude group model in a GPT / OpenAI-compatible tool.
  • Using a GPT group model in an Anthropic-compatible Claude Code setup.
  • Assuming the newest model is always best for every task.
  • Comparing only output quality while ignoring context length, speed, and cost.
  • Moving production traffic to a new model without a small test first.

​
About LLMEasy

LLMEasy gives you one place to manage API Keys, balance, and usage records. You can manage model calls from the same dashboard, but each tool still needs the protocol and Key group it supports. Quick rule:
  • Claude Code uses the Claude group and https://www.llmeasy.ru
  • Codex CLI, Cursor, Cline, OpenCode, and OpenClaw use the GPT group and https://www.llmeasy.ru/v1