ocx

Operating ocx

ocx supports local configuration and named live management workflows. Coverage is per task: provider edits, account selection, model visibility, routing reads, client integration controls and diagnostics have different transports and limits. A shared API prefix does not prove that every dashboard action has a CLI equivalent.

This skill is for operating a proxy. AGENTS_INSTALL.md covers installation and operating consent; the repository AGENTS.md covers code changes.

Find the task offline

Start at the smallest useful level; no running proxy is needed for help:

ocx help                         # compact root
ocx help models                  # family and declared children
ocx help models preset show      # exact leaf, when declared
ocx help --all                   # full top-level reference, when needed

Then read only the matching task chapter. For example, use providers/models for catalog work or Lab for local evidence. Use ocx help <family> <leaf> or appended --help, not a trailing bare help after nested operands. Missing detail can fall back to family help; it is not proof that a runtime operation is absent.

For a route you already know, an optional lookup is:

ocx capabilities --route '/api/providers/{provider}/model-costs' --json

This matches the declared path template, not a concrete provider URL or HTTP method. Exit 4 means no declaration matched. Full ocx capabilities --json and --mutating-only --json are useful for broad inventories, not mandatory preflight. Declarations describe the installed CLI; actual handlers remain the grammar authority.

Choose a workflow

Start with the named read or preview, then follow its recipe. Help is offline; the target column describes execution. A listed write still needs authority for that task, and read-oriented probes can contact upstream services.