Get model input schema
Models
Get model input schema
Return the input parameter schema for a single model — types, defaults, conditional fields, and ranges. Use this before running a model.
GET
Get model input schema
Returns a normalized input schema for one model. Each field carries its
A 404 response uses the standard REST error envelope:
type, dataType, required flag, default value, options, showWhen conditional gate, and range/length limits. Use it to build a form, validate inputs client-side, or discover what fields a model accepts before estimating credits or calling POST /v1/nodes/{nodeType}/run.
This is the REST equivalent of the MCP
get_model_schema tool. Both wrap the
same buildSchemaPayload helper server-side, so the response shape is
identical across REST and MCP.Authorizations
Bearer API key. Format:
Bearer gx_your_api_key.Path parameters
Either a subModelId (e.g.
flux-2-max-text, flux-2-max-edit,
nano-banana-pro-text) or a nodeType (e.g. flux_2_max,
crop_image). For multi-mode models (those with a subModels[] array in
GET /v1/models), passing the nodeType
returns the default sub-model’s schema — pass the specific subModelId to
inspect a non-default mode. For single-mode models (gateway or utility), the
nodeType and modelId are effectively the same.Response
Echoed back from the request.
Human-readable display name.
Model category (
text-to-image, image-to-video, text-to-speech,
utility, media-understanding, etc.).Short description used in pickers.
Modality flags or feature labels for the model (e.g.
image, Premium, High Quality).Capability flags or limits (
vision, audio, promptLimit, etc.). Merged
from ui.capabilities and top-level model config.Input field definitions in display order. Each entry:
Model-wide defaults (separate from per-field
default). Currently empty for
most models; reserved for future expansion.Request
- cURL
- Node.js
- Python
Response example — success
Real response fromGET /v1/models/flux-2-max-text/schema:
Errors
| Status | Reason |
|---|---|
401 | Missing or invalid API key |
404 | Unknown modelId — use GET /v1/models to discover valid IDs |
500 | Server error while resolving model definitions |