You can now send `safety_identifier`, an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC `GetCompletionsRequest`. It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy `user` field is still accepted. See the [Security FAQ](/developers/faq/security#how-do-i-identify-which-of-my-end-users-caused-a-policy-violation).
New model Grok News