Recraft

Recraft Crisp Upscale

Name: Recraft Crisp Upscale
Brand: Recraft
Price: 0.004 USD
Availability: InStock

AI Image Editing Model

Image #2 Image-to-Image

Recraft's image enhancement model that makes images sharper and cleaner, suitable for web use or print-ready materials

Recraft Crisp Upscale API OpenAI-compatible

Base URL

https://api.lumenfall.ai/openai/v1

Model

recraft-crisp-upscale

/v1/images/edits

curl -X POST \

  https://api.lumenfall.ai/openai/v1/images/edits \

  -H "Authorization: Bearer $LUMENFALL_API_KEY" \

  -F "model=recraft-crisp-upscale" \

  -F "[email protected]" \

  -F "prompt=Add a starry night sky to this image" \

  -F "size=1024x1024"

# Response:

# { "created": 1234567890, "data": [{ "url": "https://...", "revised_prompt": "..." }] }

import OpenAI from 'openai';

import fs from 'fs';

const client = new OpenAI({

  apiKey: 'YOUR_API_KEY',

  baseURL: 'https://api.lumenfall.ai/openai/v1'

});

const response = await client.images.edit({

  model: 'recraft-crisp-upscale',

  image: fs.createReadStream('source.png'),

  prompt: 'Add a starry night sky to this image',

  size: '1024x1024'

});

// { created: 1234567890, data: [{ url: "https://...", revised_prompt: "..." }] }

console.log(response.data[0].url);

from openai import OpenAI

client = OpenAI(

    api_key="YOUR_API_KEY",

    base_url="https://api.lumenfall.ai/openai/v1"

response = client.images.edit(

    model="recraft-crisp-upscale",

    image=open("source.png", "rb"),

    prompt="Add a starry night sky to this image",

    size="1024x1024"

# { created: 1234567890, data: [{ url: "https://...", revised_prompt: "..." }] }

print(response.data[0].url)

How we handle parameters across different providers

Not every provider speaks the same language. When you send a parameter, we handle it in one of four ways depending on what the model supports:

Behavior	What happens	Example
`passthrough`	Sent as-is to the provider	style, quality
`renamed`	Same value, mapped to the field name the provider expects	prompt
`converted`	Transformed to the provider's native format	size
`emulated`	Works even if the provider has no concept of it	n, response_format

Parameters we don't recognize pass straight through to the upstream API, so provider-specific options still work.