EmAySee Submit to Oobabooga API Node With API Key_test

The _test in the name isn't a display flourish - this is a testing leftover. EmAySee Submit to Oobabooga API Node With API Key_test is the API-key variant of the local-LLM node with two small differences, and it exists in the pack because the author left their working copy in place. There's no shame in that; it's genuinely the most honest naming in the whole pack.

The two differences from its parent (EmAySee_SubmitToOobaboogaAPIWithKey):

1. A min_p field. Where the parent has top_k, typical_p, and the rest, this one adds min_p (default 0) - the minimum-probability sampler that a few modern models expect. Note the source types it as an INT with a max of 200, which is odd (min_p is normally a 0-1 float); treat values above 1 as "don't bother."
2. No single default endpoint. Instead of one default URL, api_endpoint is a dropdown wired to two of the author's LAN addresses (10.0.0.71 and 10.0.0.76). For you, this means the dropdown comes pre-populated with endpoints that will never work - you'll pick or type your own.

Everything else is inherited: apikey_input, text_input, the sampler knobs (temperature 0.7, top_p 0.9, rep penalty 1.1), max_new_tokens dropdown, seed, delay_seconds, show_api_response. Output is a single api_response string; the node is an output node, posting non-streaming to /v1/completions and returning an error string rather than crashing when the request fails.

Should you use it?

Functionally it does the same job as the plain WithKey node. The min_p knob is the only actual feature difference, and only matters if your model uses min-p sampling. If you want min_p, this node gives it to you without writing your own. Otherwise there's no reason to prefer _test over the parent - and if you grab a workflow that uses it, spend ten seconds checking which endpoint got baked in, because the dropdown defaults are somebody else's house.

Installing it

Same pack, same path: install ComfyUI_EmAySee_CustomNodes via ComfyUI Manager or git clone https://github.com/EmAySee/ComfyUI_EmAySee_CustomNodes into custom_nodes/, then restart. No dependencies, no models. It appears in the node list because the pack auto-loads every .py in its py/ folder - which is exactly why a _test node ships to everyone; there's no curation step keeping dev leftovers out.