Baiyin AI Music Generation and Task Query

Problem

Maps natural-language music requests like "write a song," "make a version from this demo," and "cover the last one" into Baiyin Open Platform AI music task API calls. It targets the failure modes around music-generation APIs: guessing model names, sending numeric values as strings, passing local paths as public url fields, and returning download links before the task has succeeded.

How It Works

• Model whitelist: Only chirp-fenix and chirp-crow are allowed. The default is chirp-fenix; if a user requests a model outside the whitelist, the skill reports unsupported instead of passing the value through.
• Task modes: Basic generation uses task=""; reference-audio generation passes a public http/https URL; cover mode requires both task="cover" and cover_clip_id.
• Public audio handling: When a user provides a local file, chat attachment, or private drive link, the skill guides the upload to the Baiyin file API first and then uses the returned data.url for the reference field.
• Field constraints: prompt must be non-empty; control_option.weirdness_constraint, style_weight, and audio_weight must be numbers between 0 and 1; cusromPrompt is fixed to true using the API’s historical spelling.
• Result retrieval: After querying the task, it prefers audio resources. If result.items contains multiple versions, it lists all audioUrl values by default, labeled as "Version 1," "Version 2," and so on, rather than selecting only the first one.

Boundaries and Caveats

Use this skill when a host environment already has a valid BAIYIN_API_KEY and needs Baiyin music generation, reference-audio generation, cover mode, task status, and balance queries. It does not replace external object storage; inaccessible audio links should be uploaded through the Baiyin file API first. Cover mode cannot rely on an external url alone and must include a cover_clip_id from a prior Baiyin result. The song should not be described as complete before the task status is succeeded.