Magnific

Magnific is the reference AI image upscaler. Brut integrates its two upscaling endpoints — Upscaler Creative and Upscaler Precision V2 — in the Upscale Image node. Brut deliberately uses only the upscalers, not Magnific's other generation endpoints.

#Get a key

Generate an API key on your Magnific dashboard (API Keys page) and paste it into ⚙ Settings → Magnific (or set MAGNIFIC_API_KEY).

You do not need the webhook secret: Brut runs on your machine and polls Magnific for results directly — no webhooks, no third-party relay, nothing in the call path but you and Magnific.

#Billing — subscription credits

The API bills credits from your Magnific subscription's allocation (for example, Premium+ includes 600K credits per year), consumed by output pixel area. Two things worth knowing:

• A credit's dollar value depends on your tier, so Brut doesn't pretend to convert: the ≈$ figure on the node is Magnific's own doc-derived pay-as-you-go equivalent — a rough ceiling, not what your plan actually charges you. On a yearly plan, your effective cost is simply your plan price spread over your usage; at studio volume upscales barely dent the allocation (a few hundred credits each against hundreds of thousands per year).
• "Unlimited" plans are unlimited in the web app only — API calls always consume credits.

Brut would happily show your credit balance and per-run points instead — but Magnific's API exposes neither on individual plans (the analytics endpoints are reserved for team tiers, and task responses carry no credit field). If Magnific ships a balance endpoint, Brut will pick it up. Until then: your Magnific dashboard is the billing truth.

#Behavior notes

• Brut sends the original file bytes — never a re-encode, never a downscale. If an image exceeds Creative's 25.3M-pixel input cap, the run fails with a clear message instead of quietly shrinking your work (use Precision V2, or crop deliberately).
• Upscales are async: they survive an engine restart and reattach, like video jobs — money spent is never output lost.
• Provider errors are surfaced verbatim on the node.