Media and social · MusicBrainz + Deezer

music.search

Searches Deezer for tracks, artists or albums and enriches with MusicBrainz identifiers. details adds album, duration, release date, preview link and MusicBrainz metadata.

Operation: POST /v1/capabilities/music.search/execute
operationId: executeMusicSearch
Typical credits: 0
Search deadline: 15 s server-side
Paging: offset
Availability: ConfiguredChecked 2026-09-23 21:02 UTC

Cost basis: Free. Availability is reported per deployment by GET /v1/catalog (available). The timestamped snapshot describes configuration, not provider uptime or your account's enabled choices. Check the catalog with your own key before a call. Credits are explained under credits and limits.

Request

Body of POST /v1/capabilities/music.search/execute, JSON, validated against the MusicSearchRequest component of the public OpenAPI document. Defaults are applied server-side, so an omitted optional field behaves exactly as its default.

Request fields of music.search
Field	Type	Required	Default	Constraints and description
query	string	yes		min length 1, max length 300
kind	"track" \| "artist" \| "album"	no	"track"
num	integer	no	10	min 1, max 25 Results per page (1-25).

Unknown keys are rejected with 400 invalid_request.

Examples

Track

curl

curl -s -X POST https://api.powerups-ai.store/v1/capabilities/music.search/execute \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"query":"bohemian rhapsody","kind":"track","num":5}'

Artist

curl

curl -s -X POST https://api.powerups-ai.store/v1/capabilities/music.search/execute \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"query":"radiohead","kind":"artist"}'

No recorded response is published for this capability yet. The envelope is the ExecuteResponse component (see sessions and records); the record keys below are what the adapter emits. A first call with the example above returns search_id, the records and the charge.

Result record

Every item in results[] carries record_id and title (contract, always present) and usually url and snippet. The keys below are the documented tier: produced deterministically by this capability, omitted when the source has no value, checked against recorded source fixtures in our test suite, and published as the MusicSearchRecord component (all optional, extra keys allowed) so generated clients type them. The wire schema itself still validates only the base keys. See stability tiers.

Record keys of music.search
Key	Type	Presence	Note
kind	"track" \| "artist" \| "album"	always
artist	string	when the source has it
album	string	when the source has it
duration	string	when the source has it	Formatted m:ss; tracks only.
explicit	boolean	when the source has it
preview_url	string	when the source has it
fans	integer	when the source has it	Artists only.
albums	integer	when the source has it	Artists only.
picture	string	when the source has it	Artists only.
tracks	integer	when the source has it	Albums only.
type	string	when the source has it	Albums only.
cover	string	when the source has it	Albums only.
country	string	when the source has it	MusicBrainz fallback.
disambiguation	string	when the source has it	MusicBrainz fallback.
musicbrainz_id	string	when the source has it	MusicBrainz fallback.

Caveats

When Deezer is unavailable the MusicBrainz fallback returns a smaller key set.
Artist details carry both title and name (equal); track and album details are unchanged.

Follow-ups

Paging: Provider offset; more fetches the next slice from the source. Send { "search_id": "…", "action": "more" } while has_more is true; tolerate an empty page and stop after a bounded number of pages.
Update: Re-run with changed parameters (merged into the stored query); page state resets, search_id stays. Params accept any subset of the request fields (MusicSearchUpdateParams).
Record actions:
- details: Album, duration, release, preview and MusicBrainz metadata.
Detail behaviour: Free provider lookup on first call; repeats are cached. details is a free provider lookup.

record action

curl -s -X POST https://api.powerups-ai.store/v1/follow-up \
  -H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
  -d '{"record_id":"rec_…","action":"details"}'

Record detail objects of this capability are provider-shaped: documented by observation, not by schema. Full follow-up semantics: follow-up.

Typed client

With types generated from the public document (see types, client and samples) the call is path-keyed and the body is checked at compile time:

TypeScript (openapi-fetch)

const { data, error } = await client.POST("/v1/capabilities/music.search/execute", {
  body: {
    "query": "bohemian rhapsody",
    "kind": "track",
    "num": 5
  },
});
if (error) throw new Error(`${error.error.code}: ${error.error.message}`);
for (const record of data.results) console.log(record.record_id, record.title);