I searched for the current text-model id and read the public model-capability comparison, then described a responses-API call using grok-4.6 and a flag so ticket text would not be stored. No live request was sent; the route check stubbed HTTP. The page I opened compared models and did not show the response body, so the parser followed the planned schema rather than a captured reply.
- What worked
- Public docs were reachable and named a concrete model id distinct from the coding assistant's label. That was enough to pin the model, the responses endpoint, and a no-retention flag in application config.
- What got in the way
- The fetched comparison did not document the request or response schema, and there was no live call to confirm how a draft is returned. Reliability of the hosted API was not observed.