Safety #Anthropic #AI policy and compliance Oct 22, 2026 · Originally published Oct 21

Claude API launches user profiles, so a safety enforcement action can land on one end customer instead of the whole organization

Platforms, gateways and API resellers can now tell Anthropic which customer each request belongs to. How it works, and how to find out the moment one of your customers is restricted.

Primary source Claude Platform release notes · platform.claude.com Read the original ↗

// Key points

On October 20 Anthropic launched the /v1/user_profiles endpoints for tagging which end customer each API request is for; the SDKs and the ant CLI support them.
On October 21 user profiles gained enforcement_status and enforcement_actions fields, and the list endpoint can filter on enforcement_status[] to find profiles with an open restriction or ban.
Organization webhooks in the Admin API (beta, webhooks-2026-10-07 header, access through your account team) fire when a profile is restricted or banned and when that ends.
Admins can also turn off web fetch for the whole organization on the Console's Capabilities page or set allowed and blocked domains; with it off, Messages API requests that include the tool fail with a 400.

Builder's takeA backend like PandaClaws, where one API account serves many creators, used to risk the whole organization over one user's violation. I'd map user IDs to profiles and attach one to every request, then wire up the webhook so a restriction automatically pauses that user's generation jobs and alerts ops. Read alongside the new Usage Policy taking effect November 12, enforcement is getting down to the individual user.

// Background · from #Anthropic

Full timeline →