Nodes/ComfyUI Reve API Integration Node/Reve API (Create/Edit/Remix)
ComfyUI Node

Reve API (Create/Edit/Remix)

This ComfyUI node doesn't run a model — it rents one (Reve API)

By lum3on·Created 12 months ago·Updated 12 months ago· 12
Reve API (Create/Edit/Remix)
  • reference_image
  • reference_images
  • image
  • metadata
operationcreate
promptA beautiful landscape
api_key
versionlatest
aspect_ratio3:2
output_formatpng
verbose_loggingfalse

The ReveAPI node is the kind of thing that makes you stop and re-read the README. It sits in your graph like a normal generation node: type a prompt, hit run, an image appears. But there's no checkpoint to download, no sampler settings, no VRAM pressure. Your GPU barely warms up. That's because this node isn't running anything locally. It's a thin client for Reve's hosted image API - your prompt leaves the machine, a model on their servers renders it, and the image comes back as a finished tensor. Same ergonomics as a local pipeline, entirely different economics.

That's the thing to understand before you get excited. ComfyUI's whole deal is local, open-weight generation with total control, and this node is the exception that proves the rule. You reach for it when you want a hosted model's quality without the hardware, or when you want to slot a cloud model into an existing graph next to your local ones. It's the same situation as Krea's API tier - the hosted model isn't quite the open weights you can run yourself, the cloud version is the product, and this node is the ComfyUI-shaped front door to it.

How it works

Under the hood the node does four things. It builds a request for one of three endpoints - /v1/image/create, /v1/image/edit, or /v1/image/remix on api.reve.com. Reference images for edit and remix get resized (max 2048px for a single edit, 1536px for remix inputs), re-encoded to your chosen format, and base64-embedded in the request. The API call goes out with your key as a Bearer token, with automatic retries on 429 and 5xx responses. The image that comes back gets converted back into a ComfyUI tensor. That's the entire mechanism - a lot of the code is polite conversation between ComfyUI's image format and the API's.

One detail worth knowing: for edits, your prompt is sent as edit_instruction, not prompt. That was a genuine bug (v1.1.1) where the edit endpoint returned HTTP 400 because the parameter name was wrong, and it's fixed now.

The three operations

The single operation dropdown swaps the whole node's behavior:

  • create - text-to-image. Costs 18 credits. Set prompt, aspect_ratio, version.
  • edit - text instruction applied to one reference_image. Costs 30 credits.
  • remix - combines 1–4 reference_images under a text prompt. Costs 30 credits. Wire a batch in via reference_images; the node validates 1–4 images.

The inputs and outputs that matter

Three required inputs: operation, prompt, and api_key - paste your key (format papi.xxxxx) straight into the node; there's no environment-variable fallback anymore since v1.2.0. Everything else is optional. aspect_ratio gives you the usual 1:1 through 16:9 set (create and remix only), output_format is png/jpeg/webp, and version defaults to latest but lets you pin dated model snapshots like reve-create@20250915. verbose_logging dumps request IDs, credit usage, and timing to the console - genuinely handy when the API is being flaky.

The node returns exactly two outputs: image (the tensor, wire it to a Save Image or Preview Image node) and metadata (a JSON string with operation, model version, request ID, and processing time). Note that the README still advertises five outputs including separate request_id and credits_remaining ports - that's stale. The shipped code returns two, and the credit/request info lives inside metadata and the verbose logs. If you were hunting for those ports, that's why you can't find them.

Installing it

No models, no heavy deps - this is the easiest kind of custom node to add. requests, Pillow, and numpy are the whole dependency list, and ComfyUI already ships the latter two.

cd ComfyUI/custom_nodes
git clone https://github.com/lum3on/ComfyUI_Reve-API.git
cd ComfyUI_Reve-API
pip install -r requirements.txt

Then restart ComfyUI. Or skip all that and use ComfyUI Manager - search for "Reve API" and hit install.

Common issues

  • "Reve API is not currently available" - the node's own error message for endpoint failures. The API itself is young and has had availability wobbles; the node points you to api.reve.com and the web app as a fallback. Check your credit balance and whether your key is papi.-prefixed.
  • Image conversion errors - reference images should be valid ComfyUI tensors in a sane size range. The API caps uploads around 10MB for edit and 5MB each for remix; the node downscales, but feeding it a 4096px monster is asking for trouble.
  • Node doesn't appear - the usual suspects: dependencies not installed, wrong custom_nodes directory, or a startup error in the ComfyUI console.

The honest verdict: this is a small, early, author-driven pack (announced on r/comfyui in late 2025 with zero community discussion since). It works and the code is tidy, but you're betting on Reve's API staying up and funded. If you just want images with no GPU and no setup, fine - just don't expect the battle-tested maturity of a year-old pack.

Categoryimage/ai

Inputs (9)

NameTypeDefaultDescription
operationCOMBOcreateSelect the Reve API operation to perform
promptSTRINGA beautiful landscapeText description for the operation
api_keySTRINGReve API key - paste your API key here
versionoptCOMBOlatestModel version to use
aspect_ratiooptCOMBO3:2Output image aspect ratio (for Create and Remix operations)
output_formatoptCOMBOpngOutput image format
reference_imageoptIMAGEReference image for Edit operation
reference_imagesoptIMAGEReference images for Remix operation (1-4 images)
verbose_loggingoptBOOLEANfalseEnable verbose logging for API interactions, performance metrics, and debugging

Outputs (2)

NameTypeDescription
imageIMAGE
metadataSTRING