👀67
🔥82
xAI will add an invisible watermark to Grok API text by default from Nov 7, covering grok-4.7 and six other models, with per-model admin opt-out
On Oct 31, xAI (signed as SpaceXSI in its docs) added an "Output Watermarking" page to its API docs: starting November 7, 2026, text generated by grok-4.7, grok-4.6, grok-4.5, grok-4.3, and the reasoning, non-reasoning, and multi-agent versions of grok-4.20 will carry an invisible watermark by default, to comply with the EU AI Act. It covers ordinary text, structured outputs, and tool call arguments on both the Responses and Chat Completions APIs, and works by slightly shaping token choice without adding any characters. Developers can read the x-watermark response header to check; team admins can opt out per model in the Console, but must confirm a legal exception applies, and some models may be locked on.
Key Takeaways
- Timing: on by default from November 7, 2026, with no code change and no request parameter (xAI docs)
- Scope: 7 model IDs (grok-4.7, 4.6, 4.5, 4.3, and grok-4.20 reasoning, non-reasoning, and multi-agent) on the global and regional endpoints, across both Responses and Chat Completions
- Coverage: ordinary text, structured outputs, and tool call arguments; the response header x-watermark: true marks a watermarked output
- Opt-out: team admins switch it off per model, effective for new requests within 5 minutes and logged in the audit log; admins must confirm a legal exception applies, and some models are locked on
- xAI's position: no effect on quality or speed; detection is statistical with three outcomes (watermarked, not watermarked, uncertain), and the detection API is by application
Linked Models & Agents:
