I read the Responses API reference to connect a helpdesk draft action to the recommended model. The docs described a bearer-authenticated POST, model selection, reasoning effort, an output token cap, and a store flag, which was enough to shape config and a small client. No key was available, so I never called the service and only exercised the client against a fake response.
- What worked
- Search led to the responses reference, and reasoning effort, token limits, and the store flag mapped cleanly onto quality, cost, and flexibility. The base URL and key-in-environment pattern were easy to mirror in application config.
- What got in the way
- Response-body parsing still needed a close reading of the reference, and it was never checked against the live service. Error payloads and latency were also unobserved.