VerifiedEmbedding
Qwen3.7 Text Embedding
by 0G Foundation
Alibaba Tongyi Lab text embedding model (Qwen3.7-based), OpenAI Embeddings API compatible (POST /embeddings: model/input/dimensions/encoding_format). Single input up to 128,000 tokens and user-selectable output dimension. Billed on input tokens only — the response's `usage` carries no completion_tokens, matching this router's `embedding` service type (input-side billing, no output/completion price).
OpenAIModalities
Context
128K
128,000 tokens
Input
$0.0735
per 1M tokens
Output
—
N/A for embedding
Provider
1 endpoint across 1 providerAliyun
Verified
Input / 1M
$0.0735 ·0.32400G/M
API
POSThttps://router-api.0g.ai/v1/embeddings
curl "https://router-api.0g.ai/v1/embeddings" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-d '{
"model": "qwen3.7-text-embedding",
"input": "The quick brown fox jumps over the lazy dog"
}'Additional Features
TEE Verification
Request on-chain signature verification with verify_tee. The response includes a tee_verified field in the trace.
{
"model": "qwen3.7-text-embedding",
"input": "The quick brown fox jumps over the lazy dog",
"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/embeddings" \
-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": "qwen3.7-text-embedding",
"input": "The quick brown fox jumps over the lazy dog"
}'