Patchline builds a user-scoped search view of your catalog so you can search by free-text query, mood, genre, BPM range, ISRC, or sonic similarity. This powers Aria’s catalog tools and the dashboard search bar. All tiers can search. Sonic-similarity ranking improves with catalog size and runs across the full catalog regardless of tier.Documentation Index
Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt
Use this file to discover all available pages before exploring further.
How to search
Web dashboard
Sidebar → Catalog → search bar at top. Type any query:Via Aria
Via MCP
catalog_search is the semantic search — pass any text query, get
ranked results.
browse_catalog is the listing endpoint — paginate through your full
catalog without a query.
What you can search by
| Query type | Example | What it returns |
|---|---|---|
| Title | "Sleeper" | Tracks with that title |
| Artist | "Mira" | Tracks by that artist |
| ISRC | GBUM71029604 | The single matching track |
| Genre / mood tags | "dreampop", "melancholy" | Tracks tagged with those |
| BPM range | "between 100 and 120" | Tracks in that range |
| Key | "F minor", "D major" | Tracks in that key |
| Time signature | "3/4", "7/8" | Tracks in that meter |
| Energy / valence | "high energy", "sad" | Tracks above/below thresholds |
| Sonic similarity | "like [track ID]" | Tracks with cosine-similar audio embeddings |
| Composite | "dreampop 76 bpm female vocal" | All conditions AND’d |
How search works
- Catalog metadata is normalized on every catalog write.
- Sonic features from sonic analysis ride alongside title, artist, ISRC, release date, and platform metadata.
- Similarity features are available for tracks with completed audio analysis.
- Results are scoped to your workspace and ranked by field match, freshness, audio similarity, and requested filters.
Examples
Find a specific track by ISRC
Find tracks for a playlist
Find similar tracks
Browse without a query
Limitations
- Search is only as good as the indexed data. Tracks without completed sonic analysis won’t match audio-feature queries.
- Embeddings are catalog-only. “Find similar tracks” works within your catalog. For cross-catalog similarity, see Scout agent.
- Index lag is ~30 seconds. A freshly imported track is searchable within ~30 seconds of import completing.
Pricing
| Action | Credit cost |
|---|---|
| Catalog search query | 0 (cached) |
catalog_search MCP call | 0 |
browse_catalog MCP call | 0 |
Related pages
- Catalog import — what goes into the index
- Catalog upload — file path
- Sonic analysis — populates audio-feature filters
- Scout agent — cross-catalog similarity
FAQ
Can I search across other users' catalogs?
Can I search across other users' catalogs?
No. Search is user-scoped. Team and label workspaces can search
across the shared workspace catalog, but not other customers’
catalogs.
Why didn't my just-imported track show up?
Why didn't my just-imported track show up?
Search can have a ~30 second lag after import. Wait a moment and refresh.
If still missing after 5 minutes, the import may have failed —
check the catalog UI for an error state.
How are similar-track results ranked?
How are similar-track results ranked?
Patchline compares audio-similarity features from completed sonic
analysis and filters out weak matches. Metadata, genre, and audience
context can also affect the ranking.
Can I save searches?
Can I save searches?
Saved searches / smart playlists are on the roadmap. v1 you re-run
the query.