by 0G Foundation
The 32K-token context tier of Baidu ERNIE 4.5 Turbo, priced the same per token as the 128K tier; text in, text out, function calling supported. The upstream does not report cached_tokens, so no cache discount applies.
40K
39,936 tokens
12K
12,288 tokens
$0.1431
per 1M tokens
$0.5724
per 1M tokens
curl "https://router-api.0g.ai/v1/chat/completions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-d '{
"model": "ernie-4.5-turbo-32k",
"messages": [
{"role": "user", "content": "Hello!"}
],
"stream": true
}'TEE Verification
Request on-chain signature verification with verify_tee. The response includes a tee_verified field in the trace.
{
"model": "ernie-4.5-turbo-32k",
"messages": [{"role": "user", "content": "Hello!"}],
"verify_tee": true
}Provider Routing
Control which provider handles your request using the X-0G-Provider-* request headers.
X-0G-Provider-Address pins a provider; X-0G-Provider-Identity pins which of its upstreams to route through — both values come from the address and provider_identity fields of GET /v1/providers. Together they address one specific upstream of one provider. Send neither and the router picks by price and health, exactly as before.
curl "https://router-api.0g.ai/v1/chat/completions" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-H "X-0G-Provider-Address: <PROVIDER_ADDRESS>" \
-H "X-0G-Provider-Identity: <UPSTREAM>" \
-H "X-0G-Provider-Sort: latency" \
-H "X-0G-Provider-Allow-Fallbacks: true" \
-d '{
"model": "ernie-4.5-turbo-32k",
"messages": [{"role": "user", "content": "Hello!"}]
}'