Unclear What the audience field's possible values are or where its output is displayed is not stated.
What
Two internal functions that format lists of commands and links no longer include curated, hidden, or per-item listed fields in their output. Instead, they now include a per-item audience field when one is present.
Why
This changes the shape of the data these listing functions produce, replacing several separate flags with a single audience field, though the finding doesn't specify what values audience can take or how it's used downstream.
Names in the bundleaudience
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on aws touched a line naming audience after this was published.
Call `GetWebIdentityToken` with `https://api.anthropic.com` as the audience, then pass the result to the SDK's federation credentials. Because `identity_token_provider` (typescript, php: `identityTokenProvider`; csharp: `IdentityTokenProvi…manage-claude/wif-providers/aws see the edit
Confirmed since
Anthropic's documentation has since written up audience, on Compliance API.
- `audience: array of Organization or Users or AnyoneWithLink`api/compliance see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the audience field's possible values are or where its output is displayed is not stated.
Anthropic's documentation agrees
Anthropic's documentation has since written up audience, on Compliance API.