Nodes
List, search, and inspect the node palette.
List or search nodes
GET /v1/nodesReturns the node palette as an array of node specs.
The node catalog is public — GET /v1/nodes and GET /v1/nodes/:id work
without a token. A spec is the published interface of a node and contains
nothing caller-specific, which is what lets
blitflow.com/models browse it. Every other
endpoint still requires a credential.
Query parameters
| Parameter | Type | Description |
|---|---|---|
q | string | Case-insensitive match against node id, title, and description |
category | string | Filter by category (e.g. image) |
limit | integer | Maximum number of results |
Example
curl "https://studio.blitflow.com/api/v1/nodes?q=sprite&category=image&limit=3"[
{
"id": "rd-fast",
"kind": "model",
"title": "RD Fast",
"category": "image",
"description": "Fast image generation…",
"inputs": {
"prompt": {
"name": "prompt",
"connector": { "id": "TEXT", "isOptional": false, "isArray": false }
}
},
"outputs": {
"image": {
"name": "image",
"connector": { "id": "IMAGE", "isOptional": false, "isArray": false }
}
}
}
]Get one node
GET /v1/nodes/:idFetches a single spec by id (e.g. rd-fast). The response is one
NodeSpec object with the full inputs/outputs port map — including
defaultValue, optionValues (enums), and minValue/maxValue constraints.
This operation is currently served through the MCP tools
and in-process clients. Over plain HTTP, fetch the palette with
GET /v1/nodes?q=<id> and match on id.
Build node inputs from the spec you just fetched — never from memory. A value
outside a port's optionValues fails validation. See Nodes &
specs.