biterp

Supported AI models

LLM models available in the bitERP chat (app.biterp.ai), with status and end-of-support dates.

This page describes the app.biterp.ai chat

The catalog below applies to the model picker in the product chat (app.biterp.ai). It does not apply to the MCP Server (mcp.biterp.ai), where the model is chosen by your own AI client, nor to the Integrations API, which does not use an LLM.

Model status

StatusMeaning
AvailableSelectable in the chat model picker
Internal useNot selectable; the platform uses it in auxiliary steps of assistance (consumes tenant credits)
End of support announcedStill selectable, with an exit date published in the "End of support" column
DiscontinuedRemoved from the catalog; anyone who had it selected has already been migrated to the substitute

Available models

Models you can choose in the chat picker.

ModelProviderStatusRelative costEnd of supportSubstitute
GPT-5.6 SolOpenAIAvailable5
GPT-5.6 TerraOpenAIAvailable2
Claude Opus 5AnthropicAvailable4
Claude Sonnet 5AnthropicAvailable3

Relative cost ranges from 1 (most economical) to 5 (most expensive). It is the same scale shown in the chat picker — not a per-token price.

How to choose a model

In the app.biterp.ai chat, use the model picker to choose which LLM the main agent runs on. The choice applies to that conversation and consumes tenant credits based on usage.

In general:

  • Models with a higher relative cost tend to have stronger reasoning for complex tasks.
  • Models with a lower relative cost prioritize cost and latency, with capacity suited to day-to-day operations.

There is no model configuration in the Integrations API or MCP — see What this page does not cover.

Internal-use models

These models do not appear in the picker. The platform uses them in auxiliary steps of assistance (for example, specialists that support the main agent). Their usage is still debited from tenant credits.

ModelProviderStatusRelative costEnd of supportSubstitute
GPT-5.6 LunaOpenAIInternal use1
Claude Haiku 4.5AnthropicInternal use2

Discontinuation policy

When a provider ships a new version (or retires the previous one), bitERP updates the chat catalog. The change does not break your selection:

  • The saved selection migrates automatically to the substitute in the same family (same provider and capability band).
  • You do not need to re-select the model after the change.
  • When an exit date is announced, it appears in the End of support column as YYYY-MM-DD. With no announced date, the column shows .

End-of-support dates depend on the provider and the catalog we consume. This page describes how we announce and migrate — it does not promise a fixed minimum notice window.

Discontinued models

History of models that left the picker. Anyone who had them selected was migrated to the substitute below.

Discontinued modelCurrent substitute
GPT-5.5GPT-5.6 Sol
GPT-5.4GPT-5.6 Terra
GPT-5.4 miniGPT-5.6 Luna
GPT-5.2GPT-5.6 Sol
GPT-5.2 chatGPT-5.6 Sol
GPT-5.1GPT-5.6 Terra
GPT-5 miniGPT-5.6 Luna
Claude Opus 4.7Claude Opus 5
Claude Opus 4.6 FastClaude Sonnet 5
Claude Sonnet 4.6Claude Sonnet 5
Claude Sonnet 4.5Claude Opus 5

What this page does not cover

  • MCP Server (mcp.biterp.ai): the server only exposes tools via the MCP protocol. The model (and token cost) is chosen by the user's AI client — Claude Desktop, Cursor, ChatGPT, and similar.
  • Integrations API: REST API for external systems. It does not involve an LLM.

On this page