fluxlisted

# Flux on RunAPI ## Choose route - For a one-off artifact or result, use the registered `flux` service in the `runapi` CLI. If the installed command catalog does not list it, stop and report the missing service instead of inventing a command. - For an app, backend, worker, library, webhook pipeline, or production codebase, go directly to **Integrate with SDK**. Never shell out to the CLI as the production runtime. ## Discover contract Authenticate, then inspect the installed command catalog and the selected operation's current contract: ```shell runapi auth status > auth.json jq -e '.authenticated == true' auth.json runapi flux --help runapi flux <operation> --help curl --fail --location https://runapi.ai/docs/api/flux/<operation>.md --output contract.md ``` If authentication is false, stop before submitting. Ask the user to provide a valid `RUNAPI_API_KEY`, or import a user-provided key from stdin with `runapi auth import-token --token -`; use interactive browser login only when the user explicitly requests it. Choose `<operation>` only from service help. Treat command help as authoritative for the installed operation, model, and top-level field roster. Treat its API Reference as authoritative for the complete request schema, nested fields, conditional rules, task behavior, and response variants. If the two surfaces disagree, stop and report the contract mismatch instead of guessing. ## Build request Create `request.json` as valid JSON using only fields accepted by t