ImagineArt 1.5: Hosted API Access, Pricing, and Queue Guide

ImagineArt 1.5 is ImagineArt's image generation model, available through the ImagineArt web interface and fal's hosted inference service. On fal, use imagineart/imagineart-1.5-preview/text-to-image with a fal API key to submit an image request. The documented service provides hosted access, with no open weights supplied for local inference. ImagineArt model guide, fal API documentation

What are the key facts about ImagineArt 1.5 on fal?

What does ImagineArt 1.5 offer through fal's API?

fal's launch announcement highlights detailed prompts, realistic lighting and surfaces, and text within generated images. It presents product imagery, posters, and editorial concepts as intended applications. These are provider-described capabilities; the announcement does not establish a universal generation-time guarantee. Launch announcement

ImagineArt's own guide positions 1.5 for photorealistic exploration and suggests moving to 1.5 Pro when a final project needs the Pro model's resolution and composition features. For an integration, that suggests a useful boundary: test 1.5 with realistic draft requirements before deciding which service should produce the final deliverable. Model guidance

The fal queue gives developers a documented request lifecycle. A submitted job can be tracked while waiting or running, and the result can be retrieved after completion. That is useful for an application that should preserve a generation request even when its user is no longer watching the initial loading screen. Queue documentation

Keep the application record simple. Store the model endpoint, prompt, selected aspect ratio, seed, and provider request identifier with the job. Use your own product status labels for the reader-facing interface, and retain the provider response for troubleshooting. These are implementation suggestions for making a generation request auditable.

What input, seed, and billing limits apply?

The cited text-to-image API schema exposes prompt, aspect_ratio, and seed. It does not document checkpoint loading, local training, or sampler selection through that endpoint. Build your input form around the fields the service actually accepts. API schema

The seed field has a specific convention: zero and minus one request randomness. If you want to record a deliberate seed, choose another supported integer and keep it with the other settings. A saved seed is useful experiment metadata, but should not become a promise that a hosted preview model will never change. Seed documentation

Cost depends on the number of images purchased. The endpoint lists a per-image rate, while ImagineArt's web app has its own credit-based access. Treat those as separate budgets when evaluating a prototype that uses one interface and a production integration that uses the other. fal pricing, ImagineArt model guide

Queue completion also needs to be distinguished from application completion. After the provider produces a result, your application still needs to store or deliver the image and associate it with the correct user request. Plan what the user sees if download or storage fails after generation has already succeeded.

How do you call the ImagineArt 1.5 API and retrieve images?

Start in fal's playground for this exact model to check the prompt and output before writing integration code. fal's launch article identifies the playground as the interactive entry point. Keep a copy of the prompt that succeeds so your first API test uses the same creative brief. Getting started announcement

Install the JavaScript client with npm install @fal-ai/client and provide FAL_KEY through your server environment. Save the following as an ES module and run it with Node.js. The example uses the subscription helper documented for the endpoint:

import { fal } from "@fal-ai/client";

const result = await fal.subscribe(
  "imagineart/imagineart-1.5-preview/text-to-image",
  { input: {
    prompt: "A documentary photograph of a potter shaping a clay bowl, soft window light, visible hand texture, quiet workshop.",
    aspect_ratio: "4:3",
    seed: 42
  } }
);
console.log(result.requestId);
console.log(result.data.images);

The client handles request progress and returns the result. Image records include the URL and may include width, height, and content type. Keep the key in a server environment; fal's documentation recommends a server-side proxy for browser or mobile applications. Endpoint integration

For jobs that should return immediately to your application, use fal.queue.submit and save its request_id. Follow the job with fal.queue.status, and retrieve it using fal.queue.result after completion. The queue guide also documents webhooks as an alternative to polling. Queue lifecycle

Decide how your app handles a refresh before opening the integration to users. A refresh should normally resume tracking the saved job instead of automatically submitting the same paid creative request again. Keep submission and result retrieval as separate actions so a temporary display problem does not immediately create another image.

Then inspect the actual output. Confirm the subject, framing, lighting, and any requested words. Record both the successful image and the attempts that failed your creative brief. That lets you estimate the cost of an accepted deliverable without treating every generation as a finished asset.

The sibling ImagineArt 1.5 Pro guide focuses on final poster composition. For organizing reusable creative inputs, use the PromptZone prompt library as a starting point for your own task-specific test set.

How does fal access compare with ImagineArt's web app?

For a different execution arrangement, consult the ComfyUI pillar. Compare the required workflow controls and deployment model alongside the price of individual generations.

What else should you know about ImagineArt 1.5 API access?

Is ImagineArt 1.5 an open model I can install locally?

The cited documentation provides hosted web and API access, without an open-weight release. Installing the fal client only installs a way to call the remote service. Model guide, API documentation

What does ImagineArt 1.5 cost on fal?

The endpoint page lists $0.03 per image at the time checked. Revisit that page before budgeting a production batch, and include the images you may discard while iterating. fal pricing

Why is my image request still in the queue?

An ImagineArt 1.5 request on fal can be IN_QUEUE, IN_PROGRESS, or COMPLETED. Track the existing request identifier through that lifecycle before deciding whether a fresh submission is necessary. Queue documentation

Sources

• ImagineArt 1.5 model documentation
• fal launch announcement
• fal model pricing and playground
• ImagineArt 1.5 endpoint documentation
• fal asynchronous inference documentation
• ImagineArt 1.5 Pro comparison

Related guides on PromptZone

• Best SDXL Models in 2026
• ComfyUI 2026: The Complete Guide
• AI Model Releases Timeline