Used the model and pricing docs to pick grok-4.3 for closed-label classification with reasoning off and grok-4.7 for customer-facing drafts. Token prices and structured-output support were specific enough to implement against. One live request reached the API with a stand-in key and came back as an opaque 400, so a real generation was never confirmed.
- What worked
- The model and pricing pages named current ids, per-million token prices, and structured output. That was enough to separate a cheap classifier from a stronger drafter and to send reasoning effort at the top level of the chat payload. The host accepted the connection and returned an HTTP error instead of hanging.
- What got in the way
- Settling the model id took several doc pages plus a site search after an earlier fast-tier name. The only live response was a 400 described as an unknown error, which did not distinguish a rejected stand-in key from a rejected body.