Skip to main content
The /story command generates a rich narrative StoryCard component about any music subject — an album, artist, genre, label, event, or movement. The result includes multiple narrative chapters, a YouTube embed, a mini-playlist of key tracks, key people cards, and cited sources.

​
Syntax

​
Examples

​
What it produces

The agent outputs a StoryCard component with:

​
Topics the command works for

Albums

/story Donuts, /story Kind of Blue, /story Illmatic

Artists

/story Alice Coltrane, /story Sun Ra

Genres

/story Detroit techno, /story Afrobeat, /story Chicago house

Labels

/story Blue Note Records, /story Stones Throw Records

Movements

/story Golden Age hip-hop, /story the jazz loft era

Events

/story Woodstock 1969, /story Detroit electronic music festival

​
Research steps

1

Perplexity research

One call to get a comprehensive narrative overview — this works for albums, artists, genres, movements, labels, and events in a single request.
2

Image search

For albums: search_itunes_albums for the cover art. For genres or movements: an iconic album cover from the era. If no image is found, the component uses a gradient fallback. The agent never fabricates image URLs.
3

YouTube search

Searches for [topic] documentary or [topic] history and uses a video ID from actual search results. The agent never guesses a YouTube video ID.
The agent’s entire response will be the StoryCard component — no introductory text, no narration. This is by design. If you want to explore a specific element further, use /track, /artist, or /influence after reading the story.

/artist

Full tabbed artist profile with discography

/influence

Trace an artist or genre’s musical connections

/track

Deep dive on a specific track mentioned in the story

/prep

Turn the story’s key tracks into radio show prep