# auray-ai/hunyuan-3d/image-to-3d `POST https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d` submits; the response carries a `request_id` and the three URLs to use next. `POST https://auray.run/auray-ai/hunyuan-3d/image-to-3d` is the same request run synchronously: the connection is held and the response is the model's OUTPUT, the same document the result URL would have answered. A request that usually takes longer than a run may hold its connection is refused `400 model_not_synchronous` there before anything is charged, naming `expected_seconds` and `wait_ceiling_seconds` — submit it to the queue instead. Past the deadline a run is `504 run_timed_out` with `X-Auray-Request-Timeout-Type: user` — the request is still alive, running and charged or, while it waits to start, not yet charged (`charged` says which) — so poll `status_url` rather than resending, or resend with the same `idempotency_key` to be handed this request again instead of a second one. A run holds one of the connections this platform, this product and your account may keep waiting; with all of them in use it is refused `429 wait_capacity` with `Retry-After` before anything is charged (`charged: false`), and retrying after that pause is safe. One of the models behind Auray's apps. Price: By tier — a mesh, textured, rigged, and the guided pair each carry their own price in credits, which GET /v1/plans serves in force as `price_keys` (`threed.`); the submit quotes the one it charges. Fields read from https://api.auray.ai/v1/openapi.json on 2026-08-31. Every error code is explained at https://auray.ai/docs/api/errors. Address: auray-ai/hunyuan-3d/image-to-3d Servers: https://queue.auray.run · https://auray.run Scope: 3d:write Auth: Authorization: Bearer auray_sk_… API enabled: yes ## Input - image_path (string, required) — The photograph to build from: the `path` that `POST /v1/uploads` with `address: "auray-ai/hunyuan-3d/image-to-3d"` answered, sent once its bytes have been PUT. A path from POST /v1/uploads; this platform never fetches a URL you give it. - tier (string, required, one of: "geometry", "textured", "rigged", "controlled-object", "controlled-character") — Required, with no default — and the refusal body carries no list of valid values, unlike video. - out_format (string, optional, default: "glb", one of: "glb", "fbx") — `fbx` only means anything on a tier that produces a skeleton. - control_type (string, optional, one of: "bbox", "pose") — Coupled to the tier rather than free — `controlled-object` takes bbox, `controlled-character` takes pose. - control_data (any, optional) — A JSON list whose shape follows control_type, never a string. For `bbox` (controlled-object): three numbers [width, height, depth] — x across, y up, z front to back — each above 0 and at most 1; they are an aspect ratio, scaled so the longest is 1.0 before the model reads them. For `pose` (controlled-character): one row of six numbers per bone, [x1, y1, z1, x2, y2, z2] from the bone's start to its end, in the same axes, the figure standing about 1.8 units tall with its feet near y = -1, at most 512 rows. The model reads these coordinates as they are and was trained on Tencent's 51-bone A-pose — this field's second worked value, in openapi.json's `examples` and on the reference page, and what the desktop sends — so start from it and move the bones: a skeleton far from it does not fail, it steers the mesh somewhere the model never learned. - num_inference_steps (integer, optional, default: 50) — More steps, more detail, a longer run. Outside 1–100 is ignored rather than refused. Documented range: 1 to 100. - seed (integer, optional) — Reuse one to get the same mesh back. Outside the range it is refused with 422 seed_out_of_range, before any charge. Documented range: 0 to 2,147,483,647. - source_name (string, optional) — A label carried through to the stored job, for your own bookkeeping. - idempotency_key (string, optional) — Your own name for this request. Send the same one twice and the second call is answered with the first request rather than charged again. `Idempotency-Key:` as a header is accepted as an alias — that is the spelling a retrying proxy replays, and the one to use when running a model on `auray.run`, where a request that outlives its connection is answered 504 and recovered by replay. Omit it and the platform mints one. ## Response A submit answers the status document (`status`: IN_QUEUE, IN_PROGRESS or COMPLETED; `request_id`; `queue_position` while queued; `logs`; `metrics`) and then, beside it: - product (string) — Which of this platform's products ran it. - provider_job_id (string) — The id the job runs under, once it has been handed to its model — possibly while still `queued`; null before. Quote it to support. - model (string) — The address that ran it, echoed back. - engine (string) — The service's own name for the model that ran, where it reports one — a catalogue model's is its `id` on GET /v1/models; null otherwise. What `model` carried before it carried the address. - attribution (string) — The credit line the model's licence requires you to show; null where none is required. - credits_charged (integer) — What this job cost. 0 on a replay, or when a pass or a promotion paid for it (`coverage` says which). - credits_quoted (integer) — What this job costs, in credits: the price it was quoted at submit. Equal to `credits_charged` once it has been charged; while it waits in the queue to start, `credits_charged` is 0 and this is what it will be charged when it starts (a cancel before then costs nothing) — and a replay of a job still waiting quotes the body that job was queued with, which is the one it runs, not the replay's. For a catalogue model it is the hold, and the settle may give part of it back — a settled read's `credits_charged` says what it finally cost. - coverage (object) — Present when a pass or a promotion paid for this job — `{"by": "pass", "pass": "seedance-2-5"}` or `{"by": "promotion"}`, and `credits_charged` is 0 — or when you hold a pass for this model that did not cover this job: `{"by": null, "miss": {"pass": "video", "why": "door"}}`, `why` being `door` (the pass does not work here) or `shape` (it does not cover this kind of job). Absent otherwise. Send `X-Auray-Covered-Only: 1` to run a job only if a pass or a promotion pays for it. - credits_remaining (integer) — The balance after it. - expected_seconds (integer) — A rough render time, for a progress bar; 0 where nothing is published. - give_up_after_seconds (integer) — The longest this job may take from its submit: the longest it may wait to start (your X-Auray-Request-Timeout, or the product's queue deadline) plus the longest it may run before it is stopped and refunded. Waiting longer is waiting for nothing; the official clients wait this long by default. For a catalogue model the part it may run is its own reap as its registry row states it (`lifecycle.stall_ceiling_seconds` on GET /v1/models); otherwise these are the published limits: we may lengthen them during an incident, never shorten them. - replayed (boolean) — `true` when your `idempotency_key` matched a job this platform already had. Nothing was charged and nothing was rendered twice. - waited (boolean) — Present when `wait` was asked for. The rest of this group comes with it. - timed_out (boolean) — The wait ran out before the job settled. Still a 2xx, never a 408 or 504 — a library that retries on those would resubmit and you would pay twice. Poll `status_url`. - wait_declined (string) — No seat was free to hold the connection with, so the request was answered at once. `platform_busy`: no product would have helped. `product_busy`: another product's queue might. `account_busy`: you are already waiting on every seat your plan's lanes allow. The job is running either way; poll it. - status_url (string) — Poll this. - response_url (string) — Fetch the result from this once the status is COMPLETED. - cancel_url (string) — `PUT` to this to ask for a cancellation. Poll `status_url`, fetch `response_url` once COMPLETED, `PUT` `cancel_url` to stop it. ## Price Price: By tier — a mesh, textured, rigged, and the guided pair each carry their own price in credits, which GET /v1/plans serves in force as `price_keys` (`threed.`); the submit quotes the one it charges. ## Paths POST https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d Run auray-ai/hunyuan-3d/image-to-3d GET https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d/requests/{request_id} The result GET https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d/requests/{request_id}/status The status PUT https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d/requests/{request_id}/cancel Ask for a cancellation ## Example ```bash curl -X POST https://queue.auray.run/auray-ai/hunyuan-3d/image-to-3d \ -H 'Authorization: Bearer auray_sk_…' \ -H 'Content-Type: application/json' \ -d '{"image_path":"…","tier":"geometry"}' ``` ## Full contract https://api.auray.ai/v1/models/auray-ai/hunyuan-3d/image-to-3d/openapi.json