An upcoming developer change
xAI’s guide, updated October 31, schedules default-on text watermarking November 7 for listed Grok API models. First publication is unverified; this is a catch-up. [1]
An API connects software services. This statistical marker changes text choices without adding characters. A response header, x-watermark: true, confirms use. Some models require watermarking; detection access is restricted and results can be uncertain. [1]
Our take
For a fictional support app, start with a made-up customer asking about a late order. Ask the developer to show where the app records the response header, then review the reply for accurate dates and promises. A watermark and a helpful, correct answer are separate questions.
Before changing a team setting, review who depends on that configuration and the provider’s opt-out conditions. Save the decision so another maintainer knows why it was made. We have not called this API, tested detection, or changed a setting.