Use the CLI when you want a terminal workflow with selected local files and explicit local actions. Use the API when you need the published request and response contract inside your own application. The clients share account controls, but they are not interchangeable command syntaxes.
The documentation is the source for installation, authentication scopes and current endpoint fields. Start there rather than adapting an unrelated provider example by changing only the URL.
Before you start
- The current CLI or API documentation and a server-published model alias.
- A scoped credential stored in your environment or secret manager, never committed to a repository.
- One short, non-sensitive prompt and a small output budget for the first real request.
Follow the steps
- Check the current installation and authentication instructions for the chosen client. Keep the credential server-side and out of browser bundles and shell transcripts.
- For the API, copy the documented chat-completions example and review the model, messages and output limit. Use the catalog’s current alias and capabilities.
- For the CLI, select the intended mode and files explicitly. A file operation requires the documented opt-in; no recursive repository upload is implied.
- Inspect the response, usage and request identifier before adding retries or concurrency. A timeout is not proof that no work occurred.
- Automate only after testing failure handling, cancellation where supported and budget limits. Follow documented idempotency instead of blindly repeating a creation request.
Use a precise prompt
Adapt to your evidence
Help review this client integration before its first request. Check that credentials stay outside source and browser code, the model alias comes from the current catalog and the output budget is explicit. Identify how the client handles timeouts, rate limits and an unknown request outcome without creating duplicate work.
Verify your work
- The actual request uses the documented endpoint and supported fields; copying an example alone is not a successful integration.
- Secrets do not appear in source, browser requests, logs or exported reports.
- Usage and errors are handled from real responses, and concurrency remains within the account’s actual service limits.
Bring your own evidence into a conversation and work through the next question.
Open chat