VerifiedChat
MiniMax-M2.5
by 0G Foundation
MiniMax-M2.5. Text in / text out, 192K-token context, thinking always on, function calling, and implicit prompt caching.
OpenAITool CallingModalities
Context
197K
196,601 tokens
Max Output
—
Input
$0.35
per 1M tokens
Output
$1.4
per 1M tokens
Provider
2 endpoints across 2 providersAliyun
Verified
Input / 1M
$0.35 ·1.54000G/M
Output / 1M
$1.4 ·6.19000G/M
Cache Read / 1M
$0.07 ·0.30800G/M
Aliyun
Verified
Input / 1M
$0.35 ·1.54000G/M
Output / 1M
$1.4 ·6.19000G/M
Cache Read / 1M
$0.07 ·0.30800G/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": "minimax-m2.5",
"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": "minimax-m2.5",
"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": "minimax-m2.5",
"messages": [{"role": "user", "content": "Hello!"}]
}'