PROMPTS BY MODALITY

Image Prompts — 1438 curated examples

Prompt examples tuned for Image generation workflows across RunAPI models. Filter by category, copy the prompt, or open the model-specific API code.

IM
Image
game-art flux-kontext-pro

Isometric game asset — medieval blacksmith shop

Isometric view of a medieval blacksmith shop for a strategy game. The building has a half-timbered structure with exposed dark wood beams and white plaster walls. The front wall is open, revealing a glowing forge, anvil, and weapon rack inside. A thatched roof with a stone chimney emits wisps of gray smoke. Surrounding details include a water barrel, stacked firewood, and a grinding wheel. The ground is cobblestone with patches of grass at the edges. Clean pixel-art-inspired style with crisp outlines and cel-shaded lighting. Transparent background for easy game engine import.

View API Code
curl -X POST https://runapi.ai/api/v1/flux_kontext/text_to_image \
  -H "Authorization: Bearer $RUNAPI_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "model": "flux-kontext-pro",
  "prompt": "Isometric view of a medieval blacksmith shop for a strategy game. The building has a half-timbered structure with exposed dark wood beams and white plaster walls. The front wall is open, revealing a glowing forge, anvil, and weapon rack inside. A thatched roof with a stone chimney emits wisps of gray smoke. Surrounding details include a water barrel, stacked firewood, and a grinding wheel. The ground is cobblestone with patches of grass at the edges. Clean pixel-art-inspired style with crisp outlines and cel-shaded lighting. Transparent background for easy game engine import."
}
JSON
FAQ

Working with Image prompts

What makes a good %{model} prompt?

A useful %{model} prompt names the subject, style, constraints, and output intent clearly. The examples here are short enough to copy, but specific enough for an agent or backend job to preserve the generation goal.

Can I reuse these prompts across models?

Often, yes. Start with a prompt in this modality, then adjust model-specific fields such as aspect ratio, duration, voice settings, or style controls. The detail page shows any saved parameters next to the prompt text.

Where do I find the right model slug?

Every card shows the RunAPI model slug. Open the model page when you want only examples for one model, or follow the model catalog link for pricing and capability details before making a request.

Can agents call these prompts directly?

Yes. After installing the RunAPI MCP Server, paste the agent instruction from a prompt detail page. The page keeps the prompt text, model slug, and endpoint path together so the agent has enough context.