comfy-api-liberation

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

comfy-api-liberation

★ 43 Open GitHub ↗

Use your own API keys with ComfyUI. No account required.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# ComfyUI API Liberation

**Use your own API keys. Break the proxy. No middleman credits.**

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![ComfyUI](https://img.shields.io/badge/ComfyUI-Custom_Node-blue)](https://github.com/comfyanonymous/ComfyUI)

---

ComfyUI's built-in API nodes don't call vendor APIs directly. They route every request through
`api.comfy.org` — a proxy that replaces vendor pricing with its own opaque credit system.
You pay Comfy.org, Comfy.org pays the vendor. This is **API laundering**.

This extension removes the middleman entirely. Your calls go direct. Your keys, your rates, your data.

</div>

## What is API Laundering?

**API laundering** is the practice of wrapping third-party APIs behind a proxy service that
substitutes the original vendor's pricing and authentication with its own credit system.
The user never interacts with the actual provider — they buy proprietary credits from the
middleman, who then makes the real API call on their behalf, pocketing the margin.

The anatomy of an API laundry:

```
┌──────────┐     credits     ┌──────────────┐     real API key     ┌──────────┐
│   User   │ ──────────────> │  Middleman   │ ──────────────────>  │  Vendor  │
│          │ <─── response── │  (proxy)     │ <──── response ────  │  (API)   │
└──────────┘                 └──────────────┘                      └──────────┘
     pays markup                  keeps margin                    receives less
     loses transparency           obscures real cost              ToS may prohibit
```

This matters because:

- **Price opacity.** You can't compare what you're paying to what the vendor charges.
  The middleman sets credit prices arbitrarily with no obligation to track vendor rate changes.
- **Vendor ToS violations.** Many API providers explicitly prohibit reselling or proxying their
  services without authorization. The middleman may be operating in a legal grey area —
  or outright violating terms they agreed to.
- **Data routing.** Your prompts, images, and generated content pass through a third party that
  has no business seeing them. The vendor's privacy policy covered a two-party relationship;
  the middleman inserted a third.
- **Artificial dependency.** The software works without the proxy. The proxy exists to create a
  billing chokepoint, not to provide functionality. If the middleman goes down, raises prices,
  or changes terms, you lose access to APIs you could have called directly.
- **Regulatory exposure.** As API resale and data brokerage come under increasing regulatory
  scrutiny, intermediaries that repackage API access without clear licensing face growing
  legal risk — risk that propagates to their users.

API laundering is not "providing a service." Providing a service means adding value.
A proxy that strips your ability to use your own API key and replaces it with a credit meter
is extracting value. The distinction matters.

## Features

- **Direct API routing** — Calls go straight to vendor APIs, not through any proxy
- **No account needed** — Works without a ComfyUI/Comfy.org account
- **Local asset storage** — Images/videos stored locally instead of uploaded to intermediary servers
- **30+ providers supported** — text, image, video, 3D, SVG, audio, and enhancement APIs
- **Simple UI** — Configure local keys or `pass` entry paths through ComfyUI's interface
- **Coverage inspector** — Review unmapped proxy endpoints and copy the full list from the UI
- **Graceful fallback** — If no key is set, falls back to default ComfyUI behavior

## Installation

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

Restart ComfyUI after installation.

## Configuration

### Option 1: UI (Recommended)

**1.** Click **API Keys** in the toolbar

**2.** Enter keys for each provider

</div>

> **Get Key** links directly to each provider's API key page
> **Status** shows "Configured" (green) or "Not set"
> The `key/pass` toggle lets each row store either a local secret or a `pass` path
> Coverage now includes a **Copy Full List** button for unmapped endpoints

### Option 2: `pass` (CLI-managed secrets)

```bash
pass insert ai/openai
pass insert ai/google
pass insert ai/elevenlabs
```

In the UI, switch a provider row from `key` to `pass` and enter the corresponding path, for example:

- `ai/openai`
- `ai/google`
- `ai/elevenlabs`

Liberation stores only the path in its config. The secret remains in your password store and is
resolved at request time with `pass show <path>`.

### Option 3: Config File

Create `api_keys.json` in the extension directory:

```json
{
  "google": { "source": "local", "value": "your-google-key" },
  "openai": { "source": "pass", "value": "ai/openai" },
  "stability": { "source": "local", "value": "your-stability-key" }
}
```

Older plain-string entries are still accepted and are treated as local keys.

### Tencent Hunyuan Credentials

Tencent Hunyuan 3D uses Tencent Cloud's signed TC3 request flow rather than a single bearer token.
For the `tencent` provider, enter one of these formats:

```text
secretId:secretKey
secretId:secretKey:region
{"secret_id":"...","secret_key":"...","region":"na-ashburn"}
```

If the region is omitted, liberation currently defaults to `na-ashburn`.

## Supported Providers

| Provider | |
|:---------|:-:|
| Google (Gemini, Veo, Imagen) | [Get Key](https://aistudio.google.com/app/apikey) |
| OpenAI (GPT, DALL-E, Sora) | [Get Key](https://platform.openai.com/api-keys) |
| Stability AI | [Get Key](https://platform.stability.ai/account/keys) |
| BFL (Flux) | [Get Key](https://api.bfl.ml) |
| Ideogram | [Get Key](https://ideogram.ai/manage-api) |
| Recraft | [Get Key](https://www.recraft.ai/docs) |
| Luma Labs | [Get Key](https://lumalabs.ai/dream-machine/api/keys) |
| ElevenLabs | [Get Key](https://elevenlabs.io/app/settings/api-keys) |
| Freepik / Magnific | [Get Key](https://docs.freepik.com/) |

</td>
<td width="33%" valign="top">

| Provider | |
|:---------|:-:|
| Runway | [Get Key](https://dev.runwayml.com) |
| Kling AI | [Get Key](https://app.klingai.com/global/dev/api-key) |
| MiniMax | [Get Key](https://platform.minimax.io) |
| Pika | [Get Key](https://pika.art/api) |
| Tripo3D | [Get Key](https://platform.tripo3d.ai) |
| Rodin (Hyper Human) | [Get Key](https://hyperhuman.deemos.com/api-dashboard) |
| Topaz Labs | [Get Key](https://www.topazlabs.com/api) |

</td>
<td width="33%" valign="top">

| Provider | |
|:---------|:-:|
| BytePlus | [Get Key](https://console.byteplus.com) |
| PixVerse | [Get Key](https://platform.pixverse.ai) |
| Vidu | [Get Key](https://platform.vidu.com) |
| Moonvalley | [Get Key](https://www.moonvalley.com) |
| LTX Studio | [Get Key](https://ltx.io/model/api) |
| Wan (Alibaba) | [Get Key](https://www.alibabacloud.com/help/en/model-studio/get-api-key) |
| Meshy | [Get Key](https://docs.meshy.ai/) |
| Reve | [Get Key](https://reve.com) |
| Bria | [Get Key](https://docs.bria.ai/) |
| Quiver | [Get Key](https://quiver.ai/start) |
| HitPaw | [Get Key](https://www.hitpaw.com/photo-enhancer-api-doc.html) |
| WaveSpeed | [Get Key](https://wavespeed.ai/docs/api-authentication) |
| Tencent Hunyuan 3D | [Docs](https://intl.cloud.tencent.com/document/product/1284) |

</td>
</tr>
</table>

## How It Works

ComfyUI's API nodes send requests to `/proxy/*` endpoints on `api.comfy.org` — the laundry.
This extension intercepts that flow and routes it where it should have gone in the first place:

1. **Intercepts** outgoing API requests before they leave ComfyUI
2. **Rewrites** `/proxy/vendor/...` URLs to direct vendor API endpoints
3. **Injects** your API key as the appropriate auth header
4. **Virtualizes** the file upload system so assets stay on your machine

All of this happens transparently — existing workflows work without modification.
No nodes to replace, no workflows to rebuild. The proxy is simply removed from the equation.

## Roadmap

- [x] Direct API routing — bypass the proxy, call vendors directly
- [x] API Key Manager UI with per-provider status
- [x] Per-provider `pass` storage mode for CLI-managed secrets
- [x] Local asset virtualization — no uploads to intermediary servers
- [x] Coverage inspector with copy-to-clipboard for unmapped endpoints
- [x] Config file support
- [x] Graceful fallback to default ComfyUI behavior when no key is set
- [x] 30+ provider mappings (Google, OpenAI, Stability, ElevenLabs, Meshy, Kling, Tencent, etc.)
- [ ] **Real pricing hints** — replace ComfyUI's opaque credit cost per node with actual vendor $/request pricing

## Debugging

```bash
LIBERATION_DEBUG=1 python main.py
```

## Security

- API keys are stored locally in `api_keys.json` (gitignored)
- `pass` mode stores only the entry path in `api_keys.json`, not the secret itself
- Keys are never sent to ComfyUI/Comfy.org servers
- Each provider only receives its own API key
- Your data travels directly between you and the vendor — no third-party pass-through

---

**MIT License** · Issues and PRs welcome

</div>

comfy-api-liberation

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README