Endpoint Configuration

Endpoint Configuration builds an ENDPOINT_CONFIG object from two strings: a base endpoint URL and an auth_token. It packages them into a small dict that also carries a pre-built Authorization: Bearer <token> header (only when a token is actually provided). It's the generic, one-off config builder in the pack - and I want to be straight with you about it, because this node is easy to misunderstand.

Here's the honest state of things: no other node in ComfyBros consumes ENDPOINT_CONFIG. The pack's RunPod nodes don't read from it - they pull endpoint configs from ComfyUI's settings file (serverlessConfig.instances), and the LLM nodes build their own connection objects. So this node produces a type that the pack itself never feeds back in. What is it for, then? Three plausible uses: you're reading the value with a text/debug node to inspect what config you assembled; you're pairing it with a different pack that happens to accept an ENDPOINT_CONFIG-shaped dict; or you're using it as a labeled, reusable holder for an endpoint + token that you'll copy values from when wiring other nodes. None of those are crazy - the node is a utility, not a pipeline stage.

Inputs

• endpoint (required) - the API base URL. Default is the placeholder https://api.example.com, which does nothing on its own.
• auth_token (required, but commonly left empty) - the bearer token. The subtle behavior: the Authorization header is only included if the token is non-empty, so a blank token yields a config with just Content-Type. That's a genuinely nice touch for endpoints that don't need auth.

Output

One output: ENDPOINT_CONFIG - a dict with endpoint, auth_token, and headers. Because the node's only real use is getting that value somewhere you can read it, you'll usually wire it to whatever inspection tool you have (a Show Text / debug node that can render a dict) or into a compatible consumer.

Installing it

ComfyBros installs like any custom node pack. ComfyUI Manager - search "ComfyBros" - or:

cd ComfyUI/custom_nodes
git clone https://github.com/turnbros/ComfyBros

Then restart ComfyUI. The README references a requirements.txt that doesn't exist; the declared deps are in pyproject.toml. The node lives under ComfyBros/Configuration.

Gotchas

The big one is the caveat above: this node's output type isn't consumed anywhere else in the pack, so if you wire it up expecting it to drive a RunPod generation node, nothing will connect. It's a standalone config holder. The other detail is the placeholder default - run it as-is and you've built a config pointing at api.example.com, which is exactly as useful as it sounds. Fill in real values, or skip this node entirely if you're using the pack's serverless-instance flow, which manages endpoints in settings instead.