Platform Reference

LLM API Compatibility Matrix|Chat, Responses, Claude and Multimodality

Distinguish between Chat Completions, Responses API, Anthropic Messages, streaming output, tool calls, Embedding, images, and video APIs to avoid misinterpreting basic chat success as full compatibility.

Updated on 2026-07-13Checked 2026-07-13Estimated reading time: 9 minutesSuitable for client selection, Agent access and compatibility verification before going online
Configuration fields were checked against public documentation. Models, prices, and capabilities can change; verify current values in the console and live API responses.
Special topic: OpenAI Compatible API Access and Troubleshooting Center

One sentence conclusion

"OpenAI Compatible" usually means that some request formats can be reused, but it does not mean that Chat Completions, Responses API, tool calls, images, videos, and Anthropic Messages are all compatible.

API capability matrix

Ability Common uses Verification key points You cannot judge based on what
Chat Completions Dialog, text generation messagesmodel, streaming return /v1/models success
Responses API Codex, tool tasks, unified response events Event structure, tool invocation, output analysis Chat request successful
Anthropic Messages Claude Code, Claude Client Anthropic path, request header, message structure OpenAI address available
SSE Streaming Output Display generated content in real time text/event-stream, proxy buffering, disconnection Non-streaming request successful
Tool Calls Agent, function call, workflow Parameter structure, tool result return, multi-round status Normal text answer is normal
Embedding Search, vector library, RAG Vector dimensions, batch input, model type Chat model exists
Graphics API Text-to-image and image editing Request fields, output URL/Base64, size Multimodal chat available
video API Video generation and task polling Asynchronous tasks, status query, result download Graphical API available

Recommended verification sequence

1. Verify certification and model list

curl https://www.aifast.hk/v1/models \
  -H "Authorization: Bearer $API_KEY"

2. Verify minimal Chat request

curl https://www.aifast.hk/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "real model copied from model listID",
    "messages": [{"role": "user", "content": "Reply only OK"}]
  }'

3. Individually verify the capabilities required by the target client

  • Codex: Focus on validating Responses API and tool events.
  • Claude Code: Focus on verifying the Anthropic Messages entry and authentication variables.
  • Dify: Validates the selected model type, credentials, and workflow nodes.
  • OpenWebUI, Chatbox, Cherry Studio: Verify Base URL auto-splicing and model ID.
  • Agent: Individually tests tool calls, long tasks, timeouts and failure recovery.

Online Judgment Criteria

Only when all the capabilities actually used by the target business pass, can the access be judged to be suitable for production. It is recommended to save:

  • Final request URL and status code.
  • response Content-Type.
  • Request ID or error text.
  • Actual model ID.
  • Client version and configuration method.
  • Streaming, tool invocation, and timeout test results.
Source checked

Reference and Check Sources

Next step

Test the current API before fixing, migrating, or creating a test key

Use a temporary, limited key to inspect model declarations, token fields, SSE, and tool calls. Review current models and pricing only when you need a replacement API.

Model Quality CheckModel PricingCreate Account