One read of Claude Developer Platformapi-20261019T193710Z
91 pages moved out of 783 read.
Pages moved
91
significant first
Pages read
783
in this capture
Captured
19:37 UTC
Corpus hash
666b1bc29b7d
corpus-hash
What this read moved
76-91 of 91, page 4 of 4This capture is too large to show at once. Changes 76-91 of 91 are below, significant first; the rest are on the following screens.
api/errors Changed · +2 / -2 lines
from line 86
8686
8787<CodeGroup>
8888 ```bash cURL
89 # Print the response headers (including request-id); discard the body
90 curl -sS -D - -o /dev/null https://api.anthropic.com/v1/messages \
89 # -i prints the response headers, including request-id, before the body
90 curl -sS -i https://api.anthropic.com/v1/messages \
9191 -H "x-api-key: $ANTHROPIC_API_KEY" \
9292 -H "anthropic-version: 2023-06-01" \
9393 -H "content-type: application/json" \
api/service-tiers Changed · +1 / -1 lines
from line 75
7575 ```
7676
7777 ```bash CLI
78 ant messages create --transform usage.service_tier --raw-output <<'YAML'
78 ant messages create <<'YAML'
7979 model: claude-opus-4-8
8080 max_tokens: 1024
8181 messages:
build-with-claude/task-budgets Changed · +2 / -2 lines
from line 59
5959
6060 ```bash CLI
6161 ant beta:messages create --beta task-budgets-2026-03-13 \
62 --stream --format jsonl <<'YAML' | jq 'select(.type == "message_delta").usage'
62 --stream <<'YAML'
6363 model: claude-opus-5-5
6464 max_tokens: 128000
6565 messages:
from line 489
489489
490490## Changing the budget mid-conversation
491491
492`task_budget` is a request-level setting. To change the budget partway through a task, for example to extend it when the user broadens the request, set a new `task_budget` in `output_config` on the next request. Keep the caching consequence in mind: the budget value participates in the rendered prompt, so a changed value does not match cache entries created under the old one (see [Feature support](https://platform.claude.com/docs/en/build-with-claude/task-budgets#feature-support) below).
492`task_budget` is a request-level setting. To change the budget partway through a task, for example to extend it when the user broadens the request, set a new `task_budget` in `output_config` on the next request. Keep the caching consequence in mind: the budget value participates in the rendered prompt, so a changed value does not match cache entries created under the old one (see [Feature support](https://platform.claude.com/docs/en/build-with-claude/task-budgets#feature-support)).
493493
494494## Task budgets are advisory, not enforced
495495
cli-sdks-libraries/cli/authentication Changed · +1 / -1 lines
from line 21
2121
2222# If the named profile you pass with --profile doesn't exist,
2323# a new named profile will be created with that name.
24ant auth login --profile <profile-name>
24ant auth login --profile work
2525```
2626
2727During the browser flow, you select an organization and then a [workspace](https://platform.claude.com/docs/en/manage-claude/workspaces). The issued token is [scoped to that workspace](https://platform.claude.com/docs/en/manage-claude/workspaces#api-keys-and-resource-scoping), so the CLI can only see resources that belong to it. Pass `--workspace-id` to bind directly and skip the picker. To work in more than one workspace, see [Switch between workspaces](https://platform.claude.com/docs/en/cli-sdks-libraries/cli/authentication#switch-between-workspaces).
cli-sdks-libraries/cli/scripting Changed · +1 / -1 lines
from line 79
7979
8080ant beta:agents:versions list \
8181 --agent-id "$FIRST_AGENT" \
82 --transform "{version,created_at}" --format jsonl
82 --format jsonl
8383```
8484
8585### Inspect errors
manage-claude/compliance-api Changed · +2 / -2 lines
from line 4
44description: Programmatic access to your organization's Claude activity, chats, files, projects, sessions in Claude apps, and users for compliance, audit, and governance.
55---
66
7The Compliance API gives Claude Enterprise and Claude Console customers programmatic access to their organization's Activity Feed. For Claude Enterprise organizations, it also covers the directory of users, roles, and groups across every linked organization; the effective settings in force for each organization; the underlying chats, files, and projects in claude.ai organizations; and sessions in Cowork, Claude Code, Claude Science, Claude for Microsoft 365, Claude in Chrome, and the Claude add-ins for Google Docs, Google Sheets, and Google Slides. Security, legal, and compliance teams use it to audit activity, retrieve or delete content, and feed events into downstream tooling.
7The Compliance API gives Claude Enterprise and Claude Console customers programmatic access to their organization's Activity Feed. For Claude Enterprise organizations, it also covers the directory of users, roles, and groups across every linked organization; the effective settings in force for each organization; the underlying chats, files, and projects in claude.ai organizations; and sessions in Cowork, Claude Code, Claude Science, Claude for Microsoft 365, the Claude add-ins for Google Docs, Google Sheets, and Google Slides, and Claude in Chrome. Security, legal, and compliance teams use it to audit activity, retrieve or delete content, and feed events into downstream tooling.
88
99<Note>
1010 Two key types unlock the Compliance API. A **Compliance Access Key** (created in claude.ai) reaches every endpoint, and an **Admin API key** (created in Claude Console) reaches the Activity Feed only. See [Which key do you need?](https://platform.claude.com/docs/en/manage-claude/compliance-api-access#which-key-do-you-need) for the full key-type comparison.
from line 55
5555
5656The Activity Feed (`GET /v1/compliance/activities`) is available to any key that carries the `read:compliance_activities` scope; see [Query the Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) for filters, pagination, and the full `Activity` object. The remaining endpoints require a Compliance Access Key carrying the relevant scope.
5757
58A Claude Enterprise tenant has one parent organization (the top-level container that centralizes identity) with linked organizations of two kinds: claude.ai organizations, where users chat and store content, and Claude Console organizations, where users manage Claude API workloads. For a key that covers the parent organization, the directory endpoints (organizations, users, roles, and groups) return data from every linked organization of either kind. The content endpoints (chats, files, projects, project attachments, and sessions) serve Claude Enterprise data only. The chat, file, and project endpoints return claude.ai chats, files, and projects. The session endpoints return transcripts of sessions on users' machines (local sessions), captured while users are signed in with their Claude Enterprise account: sessions in Cowork, Claude Code, Claude Science, Claude for Microsoft 365, Claude in Chrome, and the Claude add-ins for Google Docs, Google Sheets, and Google Slides. They also return transcripts of Cowork sessions started on claude.ai web or mobile, which run in the cloud in Anthropic-managed environments (remote sessions). A standalone Claude Console organization (one with no parent organization) is not part of a Claude Enterprise tenant; it uses Admin API keys and can query the Activity Feed only.
58A Claude Enterprise tenant has one parent organization (the top-level container that centralizes identity) with linked organizations of two kinds: claude.ai organizations, where users chat and store content, and Claude Console organizations, where users manage Claude API workloads. For a key that covers the parent organization, the directory endpoints (organizations, users, roles, and groups) return data from every linked organization of either kind. The content endpoints (chats, files, projects, project attachments, and sessions) serve Claude Enterprise data only. The chat, file, and project endpoints return claude.ai chats, files, and projects. The session endpoints return transcripts of sessions on users' machines (local sessions), captured while users are signed in with their Claude Enterprise account: sessions in Cowork, Claude Code, Claude Science, Claude for Microsoft 365, the Claude add-ins for Google Docs, Google Sheets, and Google Slides, and Claude in Chrome. They also return transcripts of Cowork sessions started on claude.ai web or mobile, which run in the cloud in Anthropic-managed environments (remote sessions). A standalone Claude Console organization (one with no parent organization) is not part of a Claude Enterprise tenant; it uses Admin API keys and can query the Activity Feed only.
5959
6060All `/v1/compliance/*` endpoints share a rate limit of 600 requests per minute per parent organization (for a standalone Claude Console organization, per organization). The local session endpoints count only against that shared limit, and the remote session endpoints carry a second request budget on top. See [429 Too Many Requests](https://platform.claude.com/docs/en/manage-claude/compliance-errors#429-too-many-requests) for the response headers and retry contract.
6161
manage-claude/compliance-faq Changed · +2 / -2 lines
from line 70
7070 </Accordion>
7171
7272 <Accordion title="Do sessions in Cowork, Claude Code, and other Claude apps and add-ins appear in the Compliance API?">
73 Yes. Cowork sessions in Claude Desktop that run on users' machines, Claude Code sessions (in the terminal, in Claude Desktop, or in an IDE extension), sessions in the Claude Science desktop app, Claude for Microsoft 365 sessions (in Excel, PowerPoint, Word, and Outlook), chats in the Claude in Chrome browser extension, and sessions in the Claude add-ins for Google Docs, Google Sheets, and Google Slides are captured while users are signed in with their Claude Enterprise account and are available through the [local session endpoints](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions). Cowork sessions started on claude.ai web or mobile, which run in the cloud in Anthropic-managed environments, are available through the [remote session endpoints](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-remote-sessions). Each family has a list endpoint that returns session metadata and a messages endpoint that returns the session transcript (user prompts, assistant responses, and tool calls and results). The local family adds a third endpoint that retrieves one session's metadata. All of these endpoints use your existing Compliance Access Key with `read:compliance_user_data`; no new key or scope is needed.
73 Yes. Cowork sessions in Claude Desktop that run on users' machines, Claude Code sessions (in the terminal, in Claude Desktop, or in an IDE extension), sessions in the Claude Science desktop app, Claude for Microsoft 365 sessions (in Excel, PowerPoint, Word, and Outlook), sessions in the Claude add-ins for Google Docs, Google Sheets, and Google Slides, and chats in the Claude in Chrome browser extension are captured while users are signed in with their Claude Enterprise account and are available through the [local session endpoints](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions). Cowork sessions started on claude.ai web or mobile, which run in the cloud in Anthropic-managed environments, are available through the [remote session endpoints](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-remote-sessions). Each family has a list endpoint that returns session metadata and a messages endpoint that returns the session transcript (user prompts, assistant responses, and tool calls and results). The local family adds a third endpoint that retrieves one session's metadata. All of these endpoints use your existing Compliance Access Key with `read:compliance_user_data`; no new key or scope is needed.
7474
7575 Local sessions are captured as their requests reach the Claude API, so nothing is installed on the device, and on-device activity that never reaches the API is not captured. Claude Code sessions authenticated with a Claude Console API key, Claude Code sessions run through a third-party cloud platform (Amazon Bedrock, Google Cloud, or Microsoft Foundry), and [Claude Code cloud sessions](https://code.claude.com/docs/en/claude-code-on-the-web), which run on cloud infrastructure instead of the user's machine, are not captured. These cloud sessions are not remote sessions, even though both run in the cloud; the remote session endpoints return Cowork sessions only. Each run of a Cowork scheduled task in the cloud is a remote session: the remote session list endpoint returns it as an [agent-owned session](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-remote-sessions) (`agent_id` is set, and `started_by_user` identifies the human who initiated the run), and the messages endpoint returns its transcript, but neither returns the task's name or schedule. Claude Code routines that run in the cloud are Claude Code cloud sessions, so the session endpoints do not return them. Organizations with [HIPAA readiness](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#hipaa-readiness) enabled get local session data for Cowork and Claude Code only, stored for 30 days, and sessions for which [zero data retention (ZDR)](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#zero-data-retention-zdr-scope) is in effect are excluded.
7676
77 The local and remote session endpoints are stable for Cowork, Claude Code, and Claude for Microsoft 365 sessions. Coverage of sessions in Claude Science, Claude in Chrome, and the Claude add-ins for Google Docs, Google Sheets, and Google Slides is in beta.
77 The local and remote session endpoints are stable for Cowork, Claude Code, and Claude for Microsoft 365 sessions. Coverage of sessions in Claude Science, the Claude add-ins for Google Docs, Google Sheets, and Google Slides, and Claude in Chrome is in beta.
7878 </Accordion>
7979
8080 <Accordion title="What do session transcripts include?">
manage-claude/data-residency Changed · +1 / -2 lines
from line 50
5050 --model claude-opus-5-5 \
5151 --max-tokens 1024 \
5252 --inference-geo us \
53 --message '{role: user, content: "Summarize the key points of this document."}' \
54 --transform '{content.#(type=="text").text,usage.inference_geo}' --format yaml
53 --message '{role: user, content: "Summarize the key points of this document."}'
5554 ```
5655
5756 ```python Python
manage-claude/user-management Changed · +1 / -0 lines
from line 19
1919| [Members](https://platform.claude.com/docs/en/manage-claude/user-management#members) and [invites](https://platform.claude.com/docs/en/manage-claude/user-management#invites) | Available; see the [Admin API guide](https://platform.claude.com/docs/en/manage-claude/admin-api) | Available (this page) |
2020| [Groups](https://platform.claude.com/docs/en/manage-claude/user-management#groups) | Not available | Available (this page) |
2121| [Custom roles](https://platform.claude.com/docs/en/manage-claude/user-management#custom-roles) | Not available | Available, read-only (this page) |
22| [Plugins](https://platform.claude.com/docs/en/manage-claude/plugins-api) | Not available | Available in beta |
2223| [Spend limits](https://platform.claude.com/docs/en/manage-claude/spend-limits-api) | Not available | Available |
2324| Usage and cost reports | Available; see the [Usage and Cost API](https://platform.claude.com/docs/en/manage-claude/usage-cost-api) | Available through the [Claude Enterprise Analytics API](https://platform.claude.com/docs/en/manage-claude/analytics-api#get-access-to-the-claude-enterprise-analytics-api) |
2425| [Workspaces](https://platform.claude.com/docs/en/manage-claude/workspaces), [API keys](https://platform.claude.com/docs/en/manage-claude/admin-api#api-keys), [rate limits](https://platform.claude.com/docs/en/manage-claude/rate-limits-api), and the other endpoints in the [Admin API guide](https://platform.claude.com/docs/en/manage-claude/admin-api) | Available | Not available |
manage-claude/wif-providers/kubernetes Changed · +1 / -1 lines
from line 152
152152 "model": "claude-opus-5-5",
153153 "max_tokens": 1024,
154154 "messages": [{"role": "user", "content": "Hello, Claude"}]
155 }' | jq -r '.content[] | select(.type == "text") | .text'
155 }'
156156 ```
157157
158158 ```python Python
manage-claude/wif-providers/spiffe Changed · +1 / -1 lines
from line 197
197197 "model": "claude-opus-5-5",
198198 "max_tokens": 1024,
199199 "messages": [{"role": "user", "content": "Hello, Claude"}]
200 }' | jq -r '.content[] | select(.type == "text") | .text'
200 }'
201201 ```
202202
203203 ```bash CLI
managed-agents/vaults Changed · +1 / -1 lines
from line 849
849849 -H "anthropic-version: 2023-06-01" \
850850 -H "anthropic-beta: managed-agents-2026-04-01" \
851851 -H "content-type: application/json" \
852 --data @- <<'EOF' > /dev/null
852 -d @- <<'EOF'
853853 {
854854 "auth": {
855855 "type": "mcp_oauth",
models/fable-5-1/whats-new-fable-5-1 Changed · +1 / -2 lines
from line 89
8989 ```
9090
9191 ```bash CLI
92 ant beta:messages create --beta mid-conversation-output-config-2026-07-01 \
93 --transform 'content.#(type=="text").text' --raw-output <<'YAML'
92 ant beta:messages create --beta mid-conversation-output-config-2026-07-01 <<'YAML'
9493 model: claude-fable-5-1
9594 max_tokens: 4096
9695 output_config:
models/haiku-5-5/migration-guide Changed · +1 / -1 lines
from line 9
99</Note>
1010
1111<Tip>
12 **Automate your migration with the Claude API skill.** In Claude Code, run `/claude-api migrate` to invoke the bundled [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model). It works for any current Claude model as the target:
12 **Automate your migration with the [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model).** It comes bundled with Claude Code and works for any current Claude model as the target:
1313
1414 Let Claude Code migrate your code for you
1515
models/opus-5-5/migration-guide Changed · +1 / -1 lines
from line 9
99</Note>
1010
1111<Tip>
12 **Automate your migration with the Claude API skill.** In Claude Code, run `/claude-api migrate` to invoke the bundled [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model). It works for any current Claude model as the target:
12 **Automate your migration with the [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model).** It comes bundled with Claude Code and works for any current Claude model as the target:
1313
1414 Let Claude Code migrate your code for you
1515
models/sonnet-5-5/migration-guide Changed · +1 / -1 lines
from line 11
1111</Note>
1212
1313<Tip>
14 **Automate your migration with the Claude API skill.** In Claude Code, run `/claude-api migrate` to invoke the bundled [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model). It works for any current Claude model as the target:
14 **Automate your migration with the [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model).** It comes bundled with Claude Code and works for any current Claude model as the target:
1515
1616 Let Claude Code migrate your code for you
1717