NAI Usage Monitor

Every node in this pack except one spends your money; NAI Usage Monitor is the one that tells you how much you have left. It has no inputs and no outputs - you can't wire it into anything, and that's not a bug. It's a dashboard node: the place you configure your NovelAI token and, at a glance, see your subscription tier, included and purchased Anlas, and your available V5 allowance. If you're running NAI generations through ComfyUI, this node is your trip meter.

Why it exists

This pack calls NovelAI's paid API for every generation (see the KB's external-api-nodes essay for the general shape of that tradeoff - per-call cost, data leaving the machine, and the "not local, through an API" objection that follows every node in this category). Anlas is NovelAI's currency, and you don't want to discover mid-batch that you're out. The Usage Monitor fetches your subscription status from NovelAI's endpoints (image.novelai.net / api.novelai.net, per the source) and renders the tier name - Paper, Tablet, Scroll, or Opus - alongside the included and purchased Anlas and the rolling V5 free-allowance percentage. It also clears the account cache after each generation, so what you see after a run reflects what you just spent.

The token, and where it lives

This is the node that lets you set your Persistent API Token (you can also do it under Settings → 4A NovelAI → Account → Token & Anlas). The token handling is the part of this pack that deserves a moment of appreciation, because API-wrapper packs are exactly where credentials go wrong. Per the README:

• The token is sent only to your local ComfyUI backend - not to any third party.
• It's stored outside workflows, at <ComfyUI user>/ComfyUI-4A-NovelAI/credentials.json.
• It is not written into workflows, generated-image metadata, browser settings, or plugin logs.

That last point matters more than it sounds. A workflow file is something you share; if your token lived inside it, every PNG you exported would leak it. Storing it in a local credentials file outside the graph is the right call, and it's worth checking that your ComfyUI install keeps that file out of any synced folder.

Getting the token

NovelAI's Persistent API Token comes from your NovelAI account settings on the website - generate one there, paste it here, and the pack can start calling the API on your behalf. Keep it private: anyone with that token can generate on your account. (The security frame from the KB applies: any node that holds a key and calls the network by design deserves a glance at what it does with the key - in this case, the local-only storage is the good version of that story.)

Install

Standard pack install - ComfyUI Manager (search 4A NovelAI) or

cd ComfyUI/custom_nodes
git clone https://github.com/tsukino4a/ComfyUI-4A-NovelAI.git ComfyUI-4A-NovelAI
cd ComfyUI-4A-NovelAI
python install.py

Restart ComfyUI, drop the node on the canvas, and paste your token. No model downloads, no extra dependencies beyond the pack's msgpack, and - unlike every generation node in this pack - checking your balance costs you nothing.