Opengateway Cli

Workflow

1. Prefer JSON output for AI-readable automation.
2. When targeting a specific database, pass --database-url <sqlite-or-postgres-url> as a global CLI flag.
3. Read the result first.
4. For create and update commands, prefer --format json so downstream agents can parse IDs and full keys.
5. For Zed, Aider, OpenHands, Codex CLI, and similar clients, point them at the gateway's compatible data-plane endpoint instead of expecting app-specific startup presets.
6. If the requested mutation command does not exist yet, stop and report the missing CLI surface instead of falling back to the removed admin HTTP model.
7. Treat AGENTS.md at the repository root as the cross-agent entrypoint for the same CLI-first rules.

Constraints

1. Do not use the web UI.
2. Do not use /api/* admin endpoints.
3. Do not reintroduce org/project/user based workflows.37:["$","$L3d",null,{"content":"$3e","frontMatter":{"name":"opengateway-cli","description":"Use when operating OpenGateway through CLI only: provider inspection, api key inspection, gateway status checks, and future CLI-first control-plane tasks. Keywords: opengateway cli, provider list, api key list, gateway status, no UI, no admin HTTP API.","argument-hint":"Describe the operation you want, for example: list providers as json, create provider openai-main, rotate api key 12, show gateway status","user-invocable":true}}]