Base URL, method, and required headers are rendered from the active protocol template for this model.

ERNIE 5.1
baidu/ernie-5.1
An efficient iteration of the flagship line, delivering major gains in reasoning, agentic handling, and search with far fewer parameters, balancing high performance and low-cost deployment.
Modality
Input / Output Pricing
$0.56 / $2.53M tokens
Context
128000
Release date
2026-05-09
Pricing
| Specification | 0 - 32K | > 32K |
|---|---|---|
| Input | $0.56/ M tokens | $0.84/ M tokens |
| Output | $2.53/ M tokens | $3.1/ M tokens |
| Cache read | $0/ M tokens | $0/ M tokens |
| Cache write | $0/ M tokens | $0/ M tokens |
Quick Start
Paste and run the sample code below. The Gate.AI API is OpenAI-compatible—most SDKs only need a new base URL. To switch models, change the model ID.
1
Get your API key
Sign in to the Gate.AI console and create a new key under "API Keys". Keep it safe and send it via the Authorization header on every request.
Create a key in the console2
Make a request
Send a POST request to the Chat Completions endpoint with a model ID and an array of messages to get a reply.
POSThttps://api.gate.ai/openai/v1/chat/completions
curl --location "https://api.gate.ai/openai/v1/chat/completions" \
--header "Authorization: Bearer {API_KEY}" \
--header "Content-Type: application/json" \
--data '{
"model": "ernie-5.1",
"messages": [
{"role": "user", "content": "Hello"}
]
}'3
Handle the response \\\\\& streaming
By default a full JSON response is returned. Add "stream": true to the request body to receive incremental chunks over SSE.
POSThttps://api.gate.ai/openai/v1/chat/completions
curl --no-buffer --location "https://api.gate.ai/openai/v1/chat/completions" \
--header "Authorization: Bearer {API_KEY}" \
--header "Content-Type: application/json" \
--data '{
"model": "ernie-5.1",
"messages": [
{"role": "user", "content": "Hello"}
],
"stream": true
}'Endpoint
POSThttps://api.gate.ai/openai/v1/chat/completions
Field
Value
Authorization
Authentication header containing the API key in the format Bearer {API_KEY}
Content-Type
Request content type, fixed to application/json
model
Model ID; the current model is ernie-5.1
messages
Ordered array of conversation messages
stream
Whether to return the result as an SSE stream