domains / families / media / muapi-media

muapi-media

combined

Discover current MuAPI image models and run one explicitly confirmed asynchronous image generation request with bounded polling. Use when an agent needs hosted image generation without hard-coding stale model endpoints or request IDs. Generate images and videos with MuAPI's schema-driven asynchronous media API while protecting keys, polling, and output downloads.

When to use

• The user wants to find a current MuAPI image model.
• An image workflow needs MuAPI's exact model endpoint rather than a remembered alias.
• The user has explicitly approved a potentially billable image-generation request.
• An asynchronous MuAPI prediction needs bounded status polling.
• Use when the user explicitly asks to generate an image or video with MuAPI.
• Use when an existing media workflow needs a hosted asynchronous API and can
• Use when the user needs to compare or switch among current media models
• Do not use this skill for text chat or for a provider whose current schema

When not to use

• This is an instruction-only skill; it does not install an SDK or background
• Models, schemas, prices, output retention, and supported fields can change;
• Generation is asynchronous and may take minutes or fail after submission.
• Output URLs can expire and may not be reusable as permanent asset links.
• A successful HTTP response does not guarantee a valid or usable media file.
• This skill does not replace human review of media quality, rights, safety, or

Skill page

Conflict

The two skills cover the same MuAPI media generation workflow but differ significantly in scope and implementation. The first skill (davepoon) is strictly limited to image generation and relies on a bundled Python CLI script (`scripts/muapi_media.py`) that abstracts away the HTTP details. The second skill (sickn33) covers both image and video generation, uses raw `curl` and `jq` commands, and provides explicit API contract details (endpoints, headers) that the first skill hides behind the CLI. Because the first skill excludes video and the second includes it, and because the second provides the underlying API mechanics while the first provides a safer, higher-level wrapper, crowning one would hide a valid alternative approach (CLI vs. raw API) and a valid scope difference (image-only vs. image+video).