Reve 2.1 Text To Image API Documentation

Reve 2.1 Text To Image API Documentation

Playground

Reve 2.1 Text-to-Image generates high-quality images from text prompts, with strong layout intelligence, accurate text rendering, and reliable composition for posters, ads, product visuals, and typography-rich designs. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

Reve 2.1 Text to Image generates detailed, layout-aware images from natural-language prompts. It is built for dense compositions, accurate text rendering, and high-resolution visual creation across editorial, marketing, product, and creative workflows.

Why Choose This?

• Detailed image generation
  Create high-quality images from natural-language prompts.

• Layout-aware composition
  Generate structured visuals with clear subject placement, visual hierarchy, and scene organization.

• Strong text rendering
  Suitable for prompts that require readable text, posters, labels, or graphic layouts.

• Standard image output
  Generated images are returned as URLs in the standard WaveSpeed prediction response.

Parameters

How to Use

1. Write your prompt — Describe the subject, composition, style, lighting, and any text that should appear in the image.
2. Choose aspect ratio — Select an aspect ratio to let the model choose the best layout.
3. Choose output format — Select png, jpeg, or webp when needed.
4. Submit — Generate the image and retrieve the output URL.

Pricing

Best Use Cases

• Editorial visuals — Generate structured visuals for articles, covers, and layout-driven creative assets.
• Marketing images — Create campaign visuals, promotional graphics, and branded content.
• Product concepts — Explore product scenes, packaging ideas, and commercial compositions.
• Text-heavy designs — Generate posters, signs, labels, and dense layouts with readable text.
• Creative image generation — Produce high-resolution visual concepts from detailed prompts.

Pro Tips

• Describe layout, hierarchy, and the relationship between major elements.
• Put exact wording in quotation marks when text must appear in the image.
• Be specific about subject placement, lighting, color palette, and visual style.
• Use png for high-quality general output, jpeg for smaller files, and webp for web-friendly images.

## Authentication

For authentication details, please refer to the [Authentication Guide](/api-authentication).

## API Endpoints

### Submit Task & Query Result

<ApiTabs submitUrl={model.submitUrl} resultUrl={model.resultUrl} payload={model.defaultValues} />

## Parameters

### Task Submission Parameters

#### Request Parameters

<RequestParams params={model.params} />

#### Response Parameters

<SubmitResponse />

#### Result Request Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| id | string | Yes | - | Task ID |

#### Result Response Parameters

| Parameter | Type | Description |
|-----------|------|-------------|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., "success") |
| data | object | The prediction data object containing all details |
| data.id | string | Unique identifier for the prediction |
| data.model | string | Model ID used for the prediction |
| data.outputs | array&lt;string \| object&gt; | Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model. |
| data.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to poll for the prediction result |
| data.status | string | Status: `created`, `processing`, `completed`, or `failed` |
| data.created_at | string | ISO timestamp of when the request was created |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |