Skip to main content
API Reference for wavespeed/wavespeed-nano-banana-pro, served by Comfy Router from WaveSpeed.

​
Request setup

Create a key in your Comfy workspace and export it as COMFY_API_KEY. For Python, run pip install comfy-sdk. For TypeScript, run npm install @comfyorg/sdk. cURL uses raw HTTP. Model ID: wavespeed/wavespeed-nano-banana-pro Endpoint: POST https://api.comfy.org/v2/models/wavespeed/wavespeed-nano-banana-pro
Router has not published an authored input schema for this model, so there is no request example to generate a snippet from. Router forwards the body to WaveSpeed unchanged: build it from WaveSpeed’s own API documentation, then send it with the Router quickstart.

​
Schema

​
Input

Router has not published an authored input schema for this model yet: GET /v2/models/wavespeed/wavespeed-nano-banana-pro/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to WaveSpeed unchanged, so WaveSpeed’s own API documentation is authoritative for the request fields, and Router does not perform model-specific input validation. Provider validation still applies.

​
Output

This schema does not declare named properties.

​
Before you ship

The SDKs create an Idempotency-Key and reuse it for automatic retries. For manual retries, reuse the original key. Router can hold the connection for up to 10 minutes. When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider, and a 413 means the request body was larger than Router accepts. Download generated assets promptly because result URLs can expire. Any size limit named in a field description above is the provider’s own bound on that field, quoted from the provider’s specification. Router applies a separate cap to the whole request body, which base64-encoded media counts against: see request body size.

Headers

Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.

Using the Router API

Model discovery, validation errors, retries, and billing.

Limitations

What Router does not do today, and what to use instead.