Midjourney On RunAPI

Use the RunAPI CLI for one-off requests and manual verification. Use the target language SDK for applications, workers, libraries, and production integrations; never shell out to the CLI as an application runtime.

Critical: Integration Runtime

• Integration work (app, backend, worker, library, Rails service, Node service, Go service, webhook pipeline, or production codebase) uses the SDK integration path for the target language.
• One-off generation, editing, transformation, manual smoke tests, debugging, or user-requested CLI runs use the CLI path with the runapi binary. For full CLI-specific agent guidance, see https://github.com/runapi-ai/cli-skill.
• Never shell out to the runapi CLI as the production runtime integration layer.

SDK integration path

When integrating Midjourney into an app, backend, worker, library, Rails service, Node service, Go service, webhook pipeline, or production workflow, check the current SDK package and official usage. Confirm install commands, client methods (create, get, run), request fields, response shape, and error classes before using CLI help or raw HTTP examples. Use a RunAPI SDK package: