Grok API Adds Request-Level Moderation

Request-level moderation gives developers more predictable control over production outputs, but it is a narrow first step rather than a fully configurable safety layer.

• –Guidelines apply only to the request that carries them, unless repeated across a conversation
• –Omitted categories retain Grok’s default moderation behavior
• –The controls can reduce reliance on external filtering for customer-facing applications
• –Multi-agent models, deferred completions, and some `stop` or `n` configurations are unsupported
• –Developers should test refusal behavior and error handling before deploying these policies broadly