Developer API Adds Custom Content Moderation Settings

The developer release notes track modifications and functional additions across the API platform. In the update dated October 27, 2026, which replaces the prior documentation timestamp from October 15, 2026, a new mechanism for adjusting content safety settings was introduced. Developers making text-based calls through either the chat completion or standard response endpoints can now supply a dedicated array specifying rules for sensitive topics. Specifically, this mechanism allows callers to dictate how the system processes adult themes, violent descriptions, and coarse language during response generation. In practice, this gives engineering teams direct influence over output filtering without relying solely on default platform safety thresholds. However, several operational factors remain unspecified in the provided update. The text does not indicate whether applying these rules affects response latency, token usage, or billing rates. Additionally, the release note does not list the acceptable parameter values, default enforcement levels if the array is omitted, or whether these adjustments are restricted to particular model tiers or account categories.