Grok & Cursor Watch: xAI API adds safety_identifier request field
Grok & Cursor Watch: xAI API adds safety_identifier request field
Series: Grok & Cursor Watch · 29 September 2026 (JST)
Summary
xAI's API release notes, published on 2026-09-28, say applications can now send safety_identifier, an opaque end-user identifier assigned by the application. The notes list Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest. xAI states that the field lets SpaceXAI attribute a policy violation to one end user rather than to the API key, and that the legacy user field is still accepted. The notes point to the Security FAQ for identifying which end user caused a violation. The source is a vendor announcement and does not independently demonstrate attribution results.
Why it matters
A shared API key does not by itself show which end user triggered a policy action. The new field is xAI's documented way to pass an application-assigned user id for that attribution, without dropping the older user field. Whether SpaceXAI attribution works as claimed is not independently shown in this source.
Source
Published 2026-09-28.
Label: Grok & Cursor Watch
Publisher: @sangojpnet / X @sangojpn
コメント
コメントを投稿