📋 API Key Status

If you've installed comfy-api-liberation and set up a few API keys, at some point you'll forget which ones you actually did. That's the entire job of APIKeyStatus: it walks through every provider the pack knows about and tells you, in one shot, which are configured and which aren't.

It's a read-only node. No inputs, nothing to set, no decision to make. It exists because the toolbar "API Keys" panel only shows you what you've scrolled to, and after you've been through ten providers it's genuinely useful to have the whole picture dumped into one string.

What comes out

The node outputs a single status_report STRING that looks roughly like this:

=== API Key Status ===

Configured:
  ✓ google (local)
  ✓ openai (pass: ai/openai)

Not configured:
  ✗ bfl
  ✗ stability
  ...

The clever bit: this is a UI-safe report. It tells you a provider is configured and how (local key vs pass path), but it never prints the actual secret. That matters, because unlike the manager node this one isn't an output node - you can wire its output straight into a text display node, a logger, or even a workflow you plan to share, and you won't leak anything.

Why you'd actually reach for it

Two scenarios. The boring one: you're mid-workflow, an API call failed, and you want to confirm you even set the key. The slightly less boring one: you're about to share a workflow that depends on Google and you want proof the setup is there before someone else downloads it and hits a wall.

It also reads straight from the same api_keys.json the manager writes to, so there's no drift - if you configured a key in the UI or via the config file, this node reflects it immediately after a restart.

Installing

Same as the whole pack, since it ships inside it:

cd ComfyUI/custom_nodes
git clone https://github.com/holo-q/comfy-api-liberation.git

Or search "comfy-api-liberation" in ComfyUI Manager and hit install. Restart ComfyUI either way. No Python dependencies, no model downloads - it's a tiny pure-Python node over a JSON file.

Gotchas

• Empty output means empty config. If the report is just the header, you haven't set any keys yet - go run the 🔑 API Key Manager with action set first.
• "Configured" is not "working." The node reports what's in the config file. If a pass path is set but the pass binary is missing, or a key was entered wrong, it still shows as configured here. The pack degrades gracefully to Comfy's own proxy when a key doesn't resolve, so a config that looks fine can still route through the credit system. This node tells you state, not success.
• It lists providers, not node types. Don't expect it to tell you which Comfy API node maps to which provider - that's what the 🔓 Liberation Status node's unmapped-endpoint report is for.

Honestly, this is a utility node you'll glance at occasionally and appreciate the day you need it. It's not exciting, and it doesn't need to be. Five minutes after installing the pack, it answers the question "wait, did I ever set my Stability key?" without you digging through config files.