Using the CLI

The deadca7 CLI is a first-class way to drive your catalog: everything you can do by hand, you can do programmatically. It’s generated from the catalog API’s OpenAPI spec, so the commands track the API exactly.

JSON-First by Design

Output is JSON on stdout – pipe it straight into other tools.
Errors are a JSON envelope on stderr.
Exit codes are stable: 1 = api, 2 = usage, 4 = timeout.
The base URL is configurable with --base-url (defaults to the local catalog API).

Imports

deadca7 imports create <url>   # start a background import, returns an import id
deadca7 imports get <id>       # poll progress: state, albums done/total, tracks, collection id

Collections and Playlists

deadca7 collections list
deadca7 collections create
deadca7 collections get <id>
deadca7 collections update <id>
deadca7 collections delete <id>

deadca7 playlists list
deadca7 playlists create
deadca7 playlists get <id>
deadca7 playlists update <id>
deadca7 playlists delete <id>

Contents and Artists

contents list supports a search term:

deadca7 contents list "miles davis"
deadca7 artists list

Piping to jq

Because output is JSON on stdout, jq is your friend:

deadca7 collections list | jq '.[] | .name'
deadca7 imports get <id> | jq '.state'

Same Operations Over REST – and for Agents

Every CLI operation is also available over the JSON REST API (/api/imports, /api/collections, /api/collections/{id}/playlists, /api/playlists/{id}/contents, /api/contents?search=..., /api/artists). And a dedicated agent SKILL can drive all of it, so an agent can discover, organize, and manage your catalog on your behalf.