PROMPTS BY MODALITY

Video Prompts — 38 curated examples

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

VI
Video
explainer happyhorse-text-to-video

Animated explainer — data flowing through nodes

Clean motion graphics animation showing data packets as small glowing orbs traveling through a network of interconnected nodes. The nodes are arranged in a tree structure, branching outward from a central server node on the left to multiple endpoint nodes on the right. Each data packet leaves a fading light trail as it travels along the connection lines. When packets reach nodes, the node pulses briefly. Color scheme uses white lines and nodes on a dark blue background, with data packets in bright cyan. The animation flows continuously from left to right, showing the concept of API request routing.

View API Code
curl -X POST https://runapi.ai/api/v1/happyhorse/text_to_video \
  -H "Authorization: Bearer $RUNAPI_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "model": "happyhorse-text-to-video",
  "prompt": "Clean motion graphics animation showing data packets as small glowing orbs traveling through a network of interconnected nodes. The nodes are arranged in a tree structure, branching outward from a central server node on the left to multiple endpoint nodes on the right. Each data packet leaves a fading light trail as it travels along the connection lines. When packets reach nodes, the node pulses briefly. Color scheme uses white lines and nodes on a dark blue background, with data packets in bright cyan. The animation flows continuously from left to right, showing the concept of API request routing."
}
JSON
FAQ

Working with Video 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.