Skip to content

Commit c13981b

Browse files
committed
docs(xai): clarify API key transport
1 parent d887a4f commit c13981b

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • docs-site/src/content/docs/reference/configuration

‎docs-site/src/content/docs/reference/configuration/providers.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -154,8 +154,8 @@ Explicit capability `false` and Responses caller-tier forwarding retain their ex
154154
### xAI Priority Processing
155155

156156
The built-in `xai` preset advertises and injects Fast only when its effective transport uses
157-
`authMode: "key"`. API-key mode uses the key transport at `https://api.x.ai/v1` and sends
158-
`service_tier: "priority"` to xAI's public Chat Completions or Responses API. `ocx login xai`
157+
`authMode: "key"`. API-key mode targets `https://api.x.ai/v1` through the `openai-chat` adapter and
158+
sends `service_tier: "priority"` through Chat Completions. `ocx login xai`
159159
instead stores OAuth credentials for the separate Grok CLI subscription-gateway flow, so OAuth
160160
remains unclassified: its catalog rows do not advertise Fast and the proxy does not inject a tier.
161161

0 commit comments

Comments
 (0)