Skip to main content

​
Partner models

Partner models are third-party models that you call with your Nunchux API key. Each provider has its own route family on api.nunchux.ai. The request and response shapes follow the provider’s own API. Code written against the provider works after you change the base URL and the key. One key and one credit balance cover every provider. You do not need an account with the provider. Partner models do not use the Nunchux performance tiers. Each model is priced on its own terms. See the model page.

​
Models

Each model page lists the model IDs to send.

​
Choosing a model

Text-to-video. Veo 3.1, Seedance 2.5 and HappyHorse generate a soundtrack with the picture. Wan 3.0 holds one shot for up to 30 seconds. Kling V3 and MiniMax H3 cover the same task. Image-to-video. Every video family animates a starting image. Wan 2.7 also takes a driving audio track. Wan 3.0 and Wan 2.7 take an optional end frame. Reference-to-video. Wan, HappyHorse and MiniMax H3 carry a subject from reference images into new footage. Wan 3.0 takes up to 10 reference images. Multi-reference and storyboard. Kling V3 Omni composes one clip from reference images, videos and elements, or a multi-shot sequence. Motion transfer. Kling V3 motion control drives a still character with the motion of a reference video. Talking avatar. HeyGen turns a photo or a HeyGen avatar into a lip-synced video, driven by audio or by a script in a chosen voice. Image generation and editing. Nano Banana generates and edits images in one synchronous call.

​
Endpoints

Each family has one submit route. The asynchronous families also have one poll route. Kling’s {capability} is one of text2video, image2video, omni-video and motion-control. Poll the same capability that you submitted to.

​
How a request works

Nano Banana is synchronous. Send one POST and read the image from the response. Every video family is asynchronous. A request has three steps.
  1. Submit. Send a POST to the submit route with your API key in the X-API-Key header. The response contains a task identifier. A 200 status means that the provider accepted the job. It does not mean that the job is complete.
  2. Poll. Send a GET to the poll route with the task identifier. Repeat until the status is terminal. Wait a few seconds between polls. Each provider uses its own status field and its own values.
  3. Download. When the status is the success value, the poll response contains the URL of the output. Output URLs expire, some within an hour. Download the output as soon as the job succeeds.
Any other value means that the job is still running. Keep polling. Each model page shows a full submit, poll and download example.

​
Billing

Each partner model is priced on its own terms, such as resolution, duration or mode. The rates are on the model page and on the pricing page. Nunchux deducts the credits when it accepts a job. When the job fails, Nunchux refunds the credits. See Credits & pricing.

​
Errors and limits

A failed submit returns an HTTP error status. See Error codes. A failed job does not return an HTTP error. The submit returns 200, and the failure appears later as the failure status in the poll response. The poll response also carries a message that explains the failure. Read it before you resubmit. When the provider cannot read an input that you referenced, such as an image URL that is not publicly reachable, the submit can return 200 with a provider error code in the body. The submit was billed. Correct the input, then submit again. Every job counts toward the simultaneous-jobs cap of your plan. See Rate limits.