What the API is, and what it is not
Anthropic released the Claude Tag API in beta on October 23, 2026, for Claude Enterprise organizations, behind the experimental-claude-tag-2026-10-21 beta header 1. Claude Tag is Claude working as a teammate in Slack: someone mentions Claude in a channel and it answers in the thread 2. The API does not call a model. It reads and changes the Claude Tag settings an owner would otherwise set by hand in claude.ai 2.
It has 14 endpoints across four resources: Slack channels, Slack workspaces, Access bundles (read-only) and bundle targets, which attach a bundle to a channel or workspace 2. A request without the beta header returns 404, as if the endpoint did not exist 2. That matters for scanners: a 404 does not prove the API is off.
The documented responses return settings records, the source of each inherited value, and bundle attachments. They do not return message content. The data risk therefore comes from what the settings let Claude reach, not from the API's own payloads.
The five settings a write key can change
Only five settings are in scope: enabled, instructions, model, environment_id and guest_policy 2. Connecting workspaces, Slack defaults, creating bundles and spend limits stay in claude.ai 2. Each one maps to a review question:
| Setting | What a change can do | Ask |
|---|---|---|
enabled | Turns Claude on in a channel | Who approves a channel? |
instructions | Sets standing behavior for the scope | Is it reviewed like a prompt change? |
model | Picks the model | Is the model on your approved list? |
environment_id | Picks the environment whose network access level governs egress | Who may widen network access? |
guest_policy | restrict, channel_only or allow (full access) in channels with guests | Is allow ever permitted? |
The egress link comes from Claude Tag's security page: outbound traffic from a channel sandbox is default-deny, and the environment's network access level is one of the allow layers 3. Attaching a bundle is the other lever. Bundles are Anthropic's Access bundles, and creating them is not in the API 2. The API can only attach existing ones.
Identity: the Admin API key is the whole story
Calls need an Admin API key with read:claude_tag for GET endpoints or write:claude_tag for POST and DELETE 2. The write scope does not grant reads 2. Only the primary owner creates the key, in claude.ai under Organization settings > API 2. Facts to put in the review:
- Scopes are fixed at creation; adding one means a new key 4.
- The secret is shown once, and the key prefix is
sk-ant-api01-4. - Keys belong to the organization and keep working after the creator leaves 2.
- A primary owner can create a key that reaches every linked organization or one restricted to a single organization 4.
Choose the single-organization form. Anthropic's IP allowlist covers the Admin API and Compliance API only "with a key that covers only this organization" 5. A parent-wide key may fall outside that control; confirm with your account team. The allowlist is beta, takes up to 15 minutes to apply and holds up to 1,000 entries 5. Anthropic also advises short key expiration, since an allowlist limits where a key works, not for how long 5. The Enterprise key steps I read list a name and scopes only, so ask whether expiry is offered.
The Claude Tag runtime has its own identity model. In channels Claude acts under service accounts, not the requester's account, and a connector's credential is shared by everyone in the channels where it applies 3. Anthropic says each credential's use is logged 6. Review that separately from the API.
Data the feature sits on
Claude Tag retains channel memory and session transcripts, so it is not available to organizations with Zero Data Retention, a CMEK policy, or the HIPAA configuration on Claude Code and Cowork local mode 3. Check your organization's status first. If one of those applies, the question is moot.
Credentials you provision stay out of the sandbox. Agent Proxy injects them at request time and blocks requests that no allow layer covers 3. Setup screens are write-only 3. An allow-all * domain admits requests to any host on the listed ports, still without credentials 3.
Note two gaps. The IP allowlist does not cover Claude in Slack 5. And one-to-one DMs from members with a connected Claude account run on that member's own account, outside the organization spend limit 7. A policy written for channels does not describe DMs.
Evidence a reviewer will want
- Key register: name, scopes, owner, single-organization or parent-wide, creation date, rotation date, and where the secret is stored.
- A diff of Claude Tag settings per channel and workspace, taken from
GETcalls before and after rollout, withsourcesshowing where each value comes from. - Egress evidence: environment network level, allowed domains, and any
*entries. - Anthropic's security center report, if you use it. It compares settings with Anthropic's recommended configuration and exports as a report for auditors; it is beta guidance, not a certification 8.
- Change records for the key's callers. If an approval workflow turns channels on, keep the ticket ID beside each write.
The open question is audit coverage. The pages I read say the Compliance API Activity Feed records allowlist changes 5, but do not say whether Claude Tag settings changed through this API appear there. Get that answer in writing before you rely on it.
Keeping your own side of the workflow on record
The Claude Tag API is an organization-admin API in claude.ai, and Claude Tag work bills to your Anthropic usage balance under its own spend limit 7. A gateway in front of your applications' model calls will not see it. If your approval workflow runs on INFRO's management API or MCP server, INFRO's audit log (opens in a new tab) records member, key and policy changes with actor and timestamp 9. That covers INFRO's side of the workflow, not Anthropic's.
