VerifiedChat
GLM-5-Turbo
by 0G Foundation
Zhipu AI GLM-5-Turbo, the low-latency turbo variant of GLM-5. Text in / text out, 195K-token context, hybrid reasoning with a deep-thinking mode, function calling, structured output, and implicit prompt caching.
OpenAITool CallingModalities
Context
195K
195,000 tokens
Max Output
—
Input
$1.17
per 1M tokens
Output
$3.9
per 1M tokens
Provider
2 endpoints across 2 providersTencent
Verified
Input / 1M
$1.17 ·5.17000G/M
Output / 1M
$3.9 ·17.25000G/M
Cache Read / 1M
$0.234 ·1.03400G/M
Tencent
Verified
Input / 1M
$1.17 ·5.17000G/M
Output / 1M
$3.9 ·17.25000G/M
Cache Read / 1M
$0.234 ·1.03400G/M
API
POSThttps://router-api.0g.ai/v1/chat/completions
curl "https://router-api.0g.ai/v1/chat/completions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-d '{
"model": "glm-5-turbo",
"messages": [
{"role": "user", "content": "Hello!"}
],
"stream": true
}'Additional Features
TEE Verification
Request on-chain signature verification with verify_tee. The response includes a tee_verified field in the trace.
{
"model": "glm-5-turbo",
"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": "glm-5-turbo",
"messages": [{"role": "user", "content": "Hello!"}]
}'