VQV Signal
According to a post on X by @thenewstack, which cites a report from The New Stack, xAI has reversed its plan to turn on text watermarking for the Grok API by default from Nov. 7. The feature will now be opt-in, so developers receive watermarked text only if they request it. The change comes as an EU regulatory deadline approaches.
According to a post on X by @thenewstack, which cites a report from The New Stack, xAI has reversed its plan to turn on text watermarking for the Grok API by default from Nov. 7. The feature will now be opt-in, so developers receive watermarked text only if they request it. The change comes as an EU regulatory deadline approaches.
AI-assisted summary based on the listed source.
The New Stack reports xAI reversed its plan to turn on Grok API text watermarking by default from Nov. 7, making it opt-in instead, as an EU regulatory deadline approaches. Why it matters: Developers using Grok's API won't get watermarked text unless they ask for it, which matters for EU AI labeling rules....
Developers building on Grok's API will not get watermarked text unless they explicitly ask for it, which changes the default they may have planned around. Because the change relates to EU AI labeling rules, teams serving EU users may need to check whether they should opt in. Watch for how xAI documents the opt-in setting and whether the EU deadline brings further changes.
Teams using AI at work may want to compare this against current productivity and review workflows.
VQV organizes public signals from inspectable sources. It does not independently verify the underlying report.
Signal Strength reflects source quality, relevance, freshness and evidence. Public Interest helps organize discovery; it is not proof of truth.
VQV surfaced this signal because it is recent, relevant to Consumer AI, connected to Scobleizer News Pulse (X).
No login, cookies, social SDKs, or automatic posting.
