Skip to main content
GET
Get model input schema
Returns a normalized input schema for one model. Each field carries its 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 catalog source as MCP, so the response shape is consistent across public interfaces.
Use the returned fields and capabilities to discover the selected model’s current controls, defaults, accepted values, and limits. Fetch model pricing for its billing rules and a sample-input estimate.

Authorizations

string
required
Bearer API key. Format: Bearer gx_your_api_key.

Path parameters

string
required
Either a subModelId (e.g. nano-banana-pro-text, nano-banana-pro-edit, gpt-image-2-text) or a nodeType (e.g. nano_banana_pro, 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

string
Echoed back from the request.
string
Human-readable display name.
string
Model category (text-to-image, image-to-video, text-to-speech, utility, media-understanding, etc.).
string
Short description used in pickers.
object
Capability flags or limits (vision, audio, promptLimit, etc.). Merged from ui.capabilities and top-level model config.
array
Input field definitions in display order. Each entry:
object
Model-wide defaults (separate from per-field default). Currently empty for most models; reserved for future expansion.

Request

Response example — success

Real response from GET /v1/models/nano-banana-pro-text/schema:

Errors

A 404 response uses the standard REST error envelope: