API PROTOCOLS
API protocols and compatibility routes
A lot of real search demand starts from protocol terms like OpenAI-compatible API, Claude Messages API, or Gemini API, not from provider names alone. Protocol routes get closer to real integration decisions.
Protocol pages
5
Each protocol page clusters auth, base URL shape, suppliers, and next actions.
Tracked suppliers
18
These are not abstract pages. Each route connects to real suppliers.
Can continue to key checks
18
After the protocol layer, visitors can continue into direct key checks and real listing decisions.
Dataset note
Protocol routes are organized from the 2026-05-11 supplier catalog, representative models, base URLs, and checker coverage. They are here to help with integration judgment first, not replace official docs.
Protocol pages should connect new releases back to real API choices
Protocol intent often follows a new release. Keep fresh models close to the API decision instead of burying them in the long catalog.
Latest radar
Claude Sonnet 4.6
Anthropic · Claude release signal
Global model routeClaudeInput price $3Context window 1M
Why it is worth opening now：Claude Sonnet 4.6 captures freshness-driven searches that already carry obvious intent, not…
See API fit
Latest radar
Gemini 3.1 Pro Preview
Google · Gemini release signal
Global model routeGeminiInput price $2Context window 1.0M
Why it is worth opening now：Gemini 3.1 Pro Preview captures freshness-driven searches that already carry obvious intent…
See API fit
Latest radar
DeepSeek R1 0528
DeepSeek · R1 release signal
China model routeR1Input price $0.45Context window 164K
Why it is worth opening now：DeepSeek R1 0528 captures freshness-driven searches that already carry obvious intent, not…
See API fit
Latest radar
Grok 4.20
xAI · Grok release signal
Global model routeGrokInput price $3Context window 2M
Why it is worth opening now：Grok 4.20 captures freshness-driven searches that already carry obvious intent, not just br…
See API fit
Start with these mainstream protocol routes
If you arrived through terms like OpenAI Compatible API or Claude Messages API, these mainstream protocol routes are the fastest next step.
Check onboarding
OpenAI
Start with the most common onboarding and commercial-readiness probe around OpenAI.
Open pilot page
High-intent model route
Claude / Anthropic
Sample callable-model and failure-path signals around the Claude route first.
Open pilot page
Google route
Gemini / Google
Pull Gemini onboarding and route-readiness into the same early sampling lane.
Open pilot page
DeepSeek route
DeepSeek
Feed the high-frequency China-facing DeepSeek route with callable-model samples first.
Open pilot page
OpenAI-compatible API
OpenAI-compatible API routes
This is the most practical protocol route for real integration demand. Many procurement and developer decisions collapse into one question: can it plug in like OpenAI?
Auth style: Bearer token / Authorization14 providers
Endpoint shape
/v1/models + /v1/chat/completions
Representative suppliers
Anthropic Messages API
Anthropic Messages API routes
The real Anthropic question is not only whether you can buy Claude, but whether the Messages API fits your workflow, tool use, and security posture.
Auth style: x-api-key + anthropic-version1 providers
Endpoint shape
/v1/messages
Representative suppliers
Google Gemini API
Gemini API routes
Gemini becomes valuable when multimodal and long-context requirements are real, so the API shape, model coverage, and media readiness matter more than brand heat alone.
Auth style: API key query param1 providers
Endpoint shape
/v1beta/models/{model}:generateContent
Representative suppliers
GLM JWT route
GLM JWT API routes
The sticking point for GLM is often not the model itself but how JWT auth and the compatible route are implemented. Once that is clear, enterprise decisions move faster.
Auth style: JWT from API key1 providers
Endpoint shape
/api/paas/v4/chat/completions
Representative suppliers
DashScope compatible mode
DashScope compatible API routes
The Qwen route matters because DashScope exposes both native semantics and compatible mode. Many people are really asking whether they can plug it in immediately through the compatible route.
Auth style: Bearer token / compatible mode1 providers
Endpoint shape
/compatible-mode/v1/chat/completions
Representative suppliers
