by 0G Foundation
Tencent Hunyuan Hy-Image-3.0 text-to-image with reference images, billed per generated image. Synchronous: POST /v1/images/generations; one image per request (`n` must be 1). Up to 3 reference images in `image` or `images` (a string or an array of HTTP or `data:image/...` URLs). `size` is `<width>x<height>`, each side 512–2048 and at most 1024x1024 in area; omitted, the model picks one. Optional: `seed` (integer), `revise` (true/false: let the model rewrite the prompt), `footnote` (watermark text, up to 16 characters).
—
—
$0.048
per image
—
N/A for image
curl "https://router-api.0g.ai/v1/images/generations" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-d '{
"model": "tencent/hy-image-3.0",
"prompt": "A futuristic city skyline at sunset",
"n": 1,
"response_format": "b64_json"
}'
# Reference images (up to 3), e.g. to keep a character consistent: add
# "image": ["https://example.com/reference.png"]
# to the body. Each item is an http(s) URL or a data:image/...;base64,... URI.
# Response: {"data": [{"b64_json": "..."}], "x_0g_trace": {...}}
# Generation takes seconds to about a minute; the request stays open until the images are ready.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/images/generations" \
-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": "tencent/hy-image-3.0",
"prompt": "A futuristic city skyline at sunset"
}'