Skip to main content
Commands use the current context and load only the credentials they need: inference commands use the virtual key or SSO session, and administrative commands use the management credential. Run bifrost help for the full command list and bifrost <command> --help for details.

​
Inspect the gateway and your access

​
Send inference requests

​
Administer the gateway

Each resource lists its actions with bifrost <resource> --help. Mutations accept --body JSON or --file PATH. --dry-run previews a mutation, and destructive actions require --yes. For endpoints without a resource command, use the bundled OpenAPI catalog or a raw request:
bifrost request is a low-level escape hatch and does not add --dry-run or --yes safeguards.

​
Output, timeouts, and exit codes

  • --output table|json|yaml|raw selects the format. table fits the terminal and shows at most eight columns; use json or yaml for complete responses and automation.
  • --timeout (default 30s) limits a buffered request, or only the wait for response headers on a streaming request.
  • --quiet suppresses successful output, and --debug prints request diagnostics.
  • Exit codes: 0 success, 1 general or usage error, 3 authentication or authorization failure, 4 not found, 5 conflict, 6 timeout or gateway unavailable.
Generate shell completion with bifrost completion bash|zsh|fish.

​
Next steps

Contexts and credentials

Work across environments and configure CI.

Troubleshooting

Fix common authentication, context, and agent errors.