Text Model Support Matrix
The complexity of the text series lies not in “having many models,” but in “having many protocols.” The current system supports OpenAI Chat Completions, OpenAI Responses, Claude Messages, Gemini native format, Legacy Completions, and Realtime at the same time. Without a matrix, external users can easily see only the API name, without knowing which protocol they should integrate with.This page is organized by “protocol style + capability type,” rather than listing models one by one. Which models are actually available to a single API key is still determined by the result returned from Model List.
Protocol Overview
Common Model Name Examples
The following are not a “complete list of available models,” but examples of common text model names that are most likely to be encountered externally in the current system. Actual availability still depends on your channel configuration and the result returned byGET /v1/models.
OpenAI / GPT Style
Claude
Gemini
DeepSeek
Qwen
Choose an Entry Point by Protocol
1. OpenAI Chat Completions
2. OpenAI Responses
3. Claude Messages
4. Gemini Native
Choose an Interface by Capability
Conversation Generation
Realtime and Model Query
Common Model Family Mapping Approach
Selection Recommendations
- If you are already an OpenAI SDK client, start with the General Chat Interface (default streaming).
- If you need tool calling, context continuation, or structured output, prefer the OpenAI Multimodal Responses Interface.
- If you already have the Anthropic SDK, connect directly to the Claude Messages Interface.
- If you already have the Gemini SDK or need to preserve the
contents/partsstructure, connect directly to the Gemini Native Format. - If you need low-latency bidirectional voice or a real-time session, check the Realtime Interface first.
- If you are not sure which models your current key can use, check the Model List first.