Call agent
Talk to Recraft's Design Agent in a chat. This is not just any agent — it is The Design Agent, and its superpower is turning a brief — a plain description of a digital product — into a strong, consistent and genuinely amazing set of design assets. Building a coherent look normally means juggling separate tools — one for the logo, another for icons, another for social assets — and without a designer to hold it together the result feels like five apps that have never met. The Design Agent does it all at once: describe the product and it produces a full, consistent set of design assets — a logo, a colour palette, typography, an app icon and social assets among them — and can save them as a reusable Design Kit so every asset pulled from it later stays consistent. It is built for digital products: apps, websites and similar projects. Reach for it whenever the user needs a whole coherent look rather than a single one-off image. This is a two-way, turn-based conversation, not a one-shot request: you send a text message (optionally with input images) and receive the agent's combined reply, which may include images the agent generates. The agent often drives the exchange itself — instead of a final result it may reply with a clarifying question or a set of choices (for example confirming it should proceed, asking for visual references or a preferred direction, or asking which option to develop). When it does, relay that reply to the end user verbatim, collect their answer, and send it back in a follow-up call — do not answer on the user's behalf or skip ahead. A single task can take several turns before the agent produces its final design assets. Omit chat_id to start a new conversation; the response contains the chat_id — pass it in every subsequent call to continue the same conversation with full context. Images flow both ways. To send images to the agent, provide input_image_urls, a list of publicly accessible HTTP or HTTPS URLs (PNG, JPEG, WEBP or SVG); if you only have local image files, call request_upload_url first, PUT the image bytes to the returned upload URL, and pass the resulting image_url values here. Any images the agent generates come back in the response. The response contains the agent's text answer, the chat_id, URLs of any generated images with WEBP previews as base64 encoded bytes, and the credits this call used.