RTX Remix Rest API Details

Every REST API workflow in this pack needs to know one thing: where is the RTX Remix Toolkit listening? That's a host and a port, and RTX Remix Rest API Details is the node that holds them in one tidy place and hands them out. It's the pack's connection-settings panel, distilled into two fields and two outputs.

The defaults are what you want for the standard setup: address 127.0.0.1, port 8011. The Toolkit's REST API serves on localhost, and 8011 is the port the pack expects by default. If your Toolkit runs on the same machine (the usual case), you may never touch either field. If you've changed the Toolkit's REST port, or you're doing something exotic like tunneling it to another host, this is where you say so.

Inputs:

• address (STRING) - host, default 127.0.0.1.
• port (INT) - port, default 8011 (range 0–65353).

Outputs:

• address (STRING)
• port (INT)

Both pass straight through untouched - this node makes no API call. It's a constant holder, and it's meant to feed RTX Remix Start Context, which takes address and port and wraps them into the RTXRemixContext that every other REST node threads along. The pattern "Rest API Details → Start Context → your nodes → End Context" is the skeleton of every working REST workflow, and Rest API Details is where you configure the connection once so all the downstream nodes inherit it.

Worth saying: you don't strictly need Rest API Details. RTX Remix Start Context takes address and port directly, so you can wire in constants or hardcoded values. The Details node just gives you a single, obvious, well-labeled place to edit the connection without hunting through widgets. If you share workflows with other people - and this pack is easy to share - that's a real convenience: one node to tell them "change the port here."

Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix. ComfyUI Manager (search "RTX Remix") or:

cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
# restart ComfyUI

Needs ComfyUI v0.3.48+ (V3 schema). No Toolkit required for this node itself - it's pure config - but the workflows it feeds definitely are.

Where people get burned: the port. If your Toolkit's REST API is on a different port (or the Toolkit is configured to listen elsewhere), every downstream node fails with connection errors, and the fix is almost always right here. Also, if you're cloning a shared workflow, this is the first node to check when nothing connects - someone else's Toolkit may have run on a non-default port.