PROMPTS BY MODALITY

Music Prompts — 114 curated examples

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

MU
Music
psychedelic rock suno-v5.5

Psychedelic rock, phased guitars, sitar texture, hazy male v...

Psychedelic rock, phased guitars, sitar texture, hazy male vocals, swirling reverb, 60s warmth, 104 BPM

View API Code
curl -X POST https://runapi.ai/api/v1/suno/text_to_music \
  -H "Authorization: Bearer $RUNAPI_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "model": "suno-v5.5",
  "prompt": "Psychedelic rock, phased guitars, sitar texture, hazy male vocals, swirling reverb, 60s warmth, 104 BPM"
}
JSON
MU
Music
psychedelic rock suno-v4

Psychedelic Rock, Dreamy, Mellifluous

Psychedelic Rock, Dreamy, Mellifluous

View API Code
curl -X POST https://runapi.ai/api/v1/suno/text_to_music \
  -H "Authorization: Bearer $RUNAPI_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "model": "suno-v4",
  "prompt": "Psychedelic Rock, Dreamy, Mellifluous"
}
JSON
FAQ

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