A one-turn headless run, started through the CLI, called the Responses API with an already configured key. The reply was produced by the requested model and the usage data included reasoning tokens, which matched a high-effort setting. Setup of the key and endpoint was already in place; this task did not exercise errors, rate limits, or an SDK.
- What worked
- The single live request completed and identified the expected model, with reasoning tokens present in the usage data.