Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Developer Platform
One capture · api

One read of Claude Developer Platformapi-20261030T173718Z

6 pages moved out of 826 read.

Pages moved 6 significant first
Pages read 826 in this capture
Captured 17:37 UTC
Corpus hash 636ef330a616 corpus-hash

What this read moved

1-6 of 6

about-claude/api-credits-for-subscribers Changed · +15 / -15 lines

from line 1
11---
2title: API credits for Max and Team plans
2title: API credits for Max, Ultra, and Team plans
33url: https://platform.claude.com/docs/en/about-claude/api-credits-for-subscribers
4description: Claim the monthly Claude Platform credits included with Claude Max and Team plans, and learn what they cover.
4description: Claim the monthly Claude Platform credits included with Claude Max, Ultra, and Team plans, and learn what they cover.
55---
66 
7Claude Max and Team plans include monthly credits for the Claude API. To claim them, you link a [Claude Console](https://platform.claude.com/) organization to your plan. Credits then arrive in that organization each billing cycle (or monthly for annual plans), and you can use them to build and run your own applications and agents. You don’t need to add a payment method to Claude Platform.
7Claude Max, Ultra, and Team plans include monthly credits for the Claude API. To claim them, you link a [Claude Console](https://platform.claude.com/) organization to your plan. Credits then arrive in that organization each billing cycle (or monthly for annual plans), and you can use them to build and run your own applications and agents. You don’t need to add a payment method to Claude Platform.
88 
99<Note>
1010 Claude Platform on AWS, Amazon Bedrock, Google Cloud, and Microsoft Foundry: These credits apply only to the Claude API in the Claude Console. They can’t be used on other platforms.
from line 14
1414 
1515| Topic | Details |
1616| -------------------------------------- | ------------------------------------------------------------------------- |
17| **Eligible plans** | Max 5x, Max 20x, and Team, including discounted Team plans |
18| **Monthly amount** | $100 USD (Max 5x), $200 USD (Max 20x), up to $500 USD (Team, pooled\*) |
17| **Eligible plans** | Max, Ultra, and Team, including discounted Team plans |
18| **Monthly amount** | $100 USD (Max), $200 USD (Ultra), up to $500 USD (Team, pooled\*) |
1919| **Covers** | Claude API, Claude Managed Agents, the Claude Agent SDK, and playground |
2020| **Doesn’t cover** | Claude Code, extra usage in the Claude apps |
2121| **Refresh** | Each billing cycle (or monthly for annual plans) |
from line 26
2626 
2727| Plan | Monthly credit |
2828| --------------------------------------------- | -------------------------------------------------------------------- |
29| Max 5x | $100 USD |
30| Max 20x | $200 USD |
29| Max | $100 USD |
30| Ultra | $200 USD |
3131| Team, Standard seat | $20 USD per seat\* |
3232| Team, Premium seat | $100 USD per seat\* |
3333| Discounted Team plans (Nonprofit, Scientists) | Same as Team: $20 USD per Standard seat, $100 USD per Premium seat\* |
from line 47
4747 
4848You need both of the following roles:
4949 
50| Where | Required role |
51| ------------------------------- | --------------------------------------------------- |
52| **Claude plan** | Max: the subscriber<br />Team: Primary Owner, Owner |
53| **Claude Console organization** | Owner, Admin, or Billing |
50| Where | Required role |
51| ------------------------------- | ------------------------------------------------------------ |
52| **Claude plan** | Max or Ultra: the subscriber<br />Team: Primary Owner, Owner |
53| **Claude Console organization** | Owner, Admin, or Billing |
5454 
5555If you don’t have a Claude Console organization, create one in the Console at [platform.claude.com](https://platform.claude.com/) first, or create one during the claim flow.
5656 
from line 58
5858 
5959<Steps>
6060 <Step title="Open billing settings">
61 On claude.ai, go to **Settings > Billing** on a Max plan, or **Organization settings > Billing** on a Team plan.
61 On claude.ai, go to **Settings > Billing** on a Max or Ultra plan, or **Organization settings > Billing** on a Team plan.
6262 </Step>
6363 
6464 <Step title="Link a Console organization">
from line 130
130130| Change | What happens |
131131| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
132132| Cancel, downgrade to an ineligible plan, or refund | New credits stop when your plan ends. Credits you already have stay usable until they expire. |
133| Upgrade from Max 5x to Max 20x | You receive prorated API credits right away, then $200 USD each billing cycle. If you subscribe through Google Play, the $200 USD credit arrives later, by your next renewal at the latest. |
134| Upgrade from Max to Team | The Max link ends. A Team owner can claim the team's credits after the Team plan has been active for 7 days. |
133| Upgrade from Max to Ultra | You receive prorated API credits right away, then $200 USD each billing cycle. If you subscribe through Google Play, the $200 USD credit arrives later, by your next renewal at the latest. |
134| Upgrade from Max or Ultra to Team | The link to your Max or Ultra plan ends. A Team owner can claim the team's credits after the Team plan has been active for 7 days. |
135135| Add or remove Team seats | Seats added to your plan count from the next billing month’s credit. Seats you remove stay on your plan until it renews, so the credit might be lower after that. The pool stays capped at $500 USD. |
136136 
137137## Use your credits efficiently
from line 148
148148* [Rate limits and spend limits](https://platform.claude.com/docs/en/api/rate-limits)
149149* [Workspaces](https://platform.claude.com/docs/en/manage-claude/workspaces)
150150* [Pricing](https://platform.claude.com/docs/en/about-claude/pricing)
151* [Help Center: API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)
151* [Help Center: API credits for Max, Ultra, and Team plans](https://support.claude.com/en/articles/17154008)
152152 

agents-and-tools/agent-skills/overview Changed · +1 / -1 lines

from line 208
208208 
209209**Pre-built Agent Skills:** These Skills are active when you create documents. Claude uses them with no setup required.
210210 
211**Custom Skills:** Upload your own Skills as zip files through Settings > Features. Available on Pro, Max, Team, and Enterprise plans with [code execution enabled](https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude). Custom Skills are individual to each user. They are not shared organization-wide and cannot be centrally managed by admins.
211**Custom Skills:** Upload your own Skills as zip files through Settings > Features. Available on Pro, Max, Ultra, Team, and Enterprise plans with [code execution enabled](https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude). Custom Skills are individual to each user. They are not shared organization-wide and cannot be centrally managed by admins.
212212 
213213To learn more about using Skills in claude.ai, see the following resources in the Claude Help Center:
214214 

api/claude-code/routines-fire Changed · +1 / -1 lines

from line 12
1212 
1313This endpoint is the HTTP entry point. POSTing to it starts a new run of an existing routine and returns the resulting session ID and URL. Typical callers are alerting systems, CI pipelines, and internal tools that need to start a Claude Code session programmatically.
1414 
15Calling this endpoint requires a claude.ai account on a Pro, Max, Team, or Enterprise plan with [Claude Code on the web](https://code.claude.com/docs/en/claude-code-on-the-web) enabled. Authenticate with a per-routine bearer token created in the Claude Code web UI rather than a Claude API key.
15Calling this endpoint requires a claude.ai account on a Pro, Max, Ultra, Team, or Enterprise plan with [Claude Code on the web](https://code.claude.com/docs/en/claude-code-on-the-web) enabled. Authenticate with a per-routine bearer token created in the Claude Code web UI rather than a Claude API key.
1616 
1717## Differences from the Claude Platform
1818 

manage-claude/access-transparency Changed · +2 / -2 lines

from line 35
3535* **Automated processing:** Model serving, safety classifiers, and abuse-detection pipelines process your content as part of normal operation and do not generate `anthropic_access` events. Preservation initiated by automated processing does generate a `cmek_preserve` event (see [CMEK content preservation](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation)).
3636* **Your own organization’s activity:** Your API calls, admin actions, and Compliance API reads are covered by standard [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) event types.
3737* **Claude for Enterprise and Claude Apps:** claude.ai Enterprise seats, Claude for Work, Cowork, and Claude in Chrome are not covered.
38* **Claude consumer products:** Claude Free, Pro, or Max plans.
38* **Claude consumer products:** Claude Free, Pro, Max, or Ultra plans.
3939* **Partner-operated platforms:** Amazon Bedrock and Claude Models on Google Cloud (Google managed). Refer to those platforms’ transparency controls.
4040* **Anything ZDR does not cover:** Products that are not covered by ZDR (for example, the Files API, Anthropic-hosted stateful applications, and the Batch API) are not covered by Access Transparency. See [Zero data retention (ZDR)](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#zero-data-retention-zdr-scope) for additional details.
4141 
from line 176
176176| Claude API (`api.anthropic.com`) (Batch, Files) | No | The Claude API Batch and Files APIs are not covered, just like they are not covered by ZDR |
177177| Claude for Enterprise (claude.ai seats) | No | Not covered |
178178| Claude for Work | No | Not covered |
179| Claude Free, Pro, Max | No | Consumer plans are not eligible |
179| Claude Free, Pro, Max, Ultra | No | Consumer plans are not eligible |
180180| Playground (Claude Console) | No | Not covered |
181181| Microsoft Foundry | No | Not available |
182182| Amazon Bedrock, Claude Models on Google Cloud (Google managed) | No | Partner-operated platforms; refer to those platforms’ transparency controls |

manage-claude/api-and-data-retention Changed · +2 / -2 lines

from line 33
3333 
3434* **Claude Console:** Any usage in the Claude Console, including playground.
3535* **Claude Managed Agents:** Claude Managed Agents is a stateful resource; session transcripts persist until you delete them.
36* **Claude consumer products:** Claude Free, Pro, and Max plans, including when customers on those plans use Claude's web, desktop, or mobile apps or Claude Code.
36* **Claude consumer products:** Claude Free, Pro, Max, and Ultra plans, including when customers on those plans use Claude's web, desktop, or mobile apps or Claude Code.
3737* **Claude Teams and Claude Enterprise product interfaces:** These interfaces are not ZDR-eligible. The one exception is Claude Code on Claude Enterprise, which has its own ZDR offering, separate from the ZDR arrangement described on this page. That offering is available only to qualified accounts on Claude Enterprise and requires separate enablement by Anthropic. See the [Claude Code ZDR documentation](https://code.claude.com/docs/en/zero-data-retention), which applies to Claude Enterprise organizations only.
3838* **Claude for Excel:** Not currently ZDR-eligible.
3939* **Claude Fable 5.1, Claude Mythos 5.1, Claude Fable 5, and Claude Mythos 5:** These models require 30-day data retention and are not available under ZDR unless expressly authorized by Anthropic. See [Model-specific data retention requirements](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#model-specific-data-retention-requirements).
from line 60
6060 
6161### What HIPAA readiness does not cover
6262 
63* **Claude consumer products:** Claude Free, Pro, and Max plans.
63* **Claude consumer products:** Claude Free, Pro, Max, and Ultra plans.
6464* **Claude Console:** Usage through the Claude Console interface (enabling HIPAA readiness from Console settings is supported; processing PHI through the Console is not covered).
6565* **Partner-operated platforms:** Amazon Bedrock and Google Cloud’s Agent Platform. Refer to those platforms’ compliance documentation.
6666* **Claude Platform on AWS:** HIPAA readiness is not available on Claude Platform on AWS.

release-notes/overview Changed · +1 / -1 lines

from line 73
7373* We’ve launched **Claude Haiku 5.5** (`claude-haiku-5-5`), our most capable model tuned for high-volume and latency-sensitive work. It has a [1M token context window](https://platform.claude.com/docs/en/build-with-claude/context-windows), 128k max output tokens, and [adaptive thinking](https://platform.claude.com/docs/en/build-with-claude/thinking) with the [effort parameter](https://platform.claude.com/docs/en/build-with-claude/effort). It’s available on the Claude API, [Claude in Amazon Bedrock](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock), [Claude Platform on AWS](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws), [Claude on Google Cloud](https://platform.claude.com/docs/en/build-with-claude/claude-models-on-google-cloud/google-managed), and [Claude in Microsoft Foundry](https://platform.claude.com/docs/en/build-with-claude/claude-in-microsoft-foundry). See [What’s new in Claude Haiku 5.5](https://platform.claude.com/docs/en/models/haiku-5-5/whats-new-haiku-5-5).
7474* Code written for Claude Haiku 4.5 can break on Claude Haiku 5.5. Manual extended thinking (`budget_tokens`), the sampling parameters `temperature`, `top_p`, and `top_k`, and assistant message prefill can each return a 400 error. `computer_20250124` also returns a 400 error: use the `computer_toolset_20260801` toolset on the Claude API and Google Cloud, or `computer_20251124` on Amazon Bedrock. A request that sends thinking blocks back after a change to `system`, `tools`, or earlier turns can also return a 400 error. Adaptive thinking is on by default, so a response can begin with `thinking` blocks, and their text is omitted unless you set `thinking.display` to `"summarized"`. The same text also counts as more tokens. See the [migration guide](https://platform.claude.com/docs/en/models/haiku-5-5/migration-guide) for each change. For model-specific prompting patterns, see [Prompting Claude Haiku 5.5](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-haiku-5-5).
7575* The Python and TypeScript SDKs now include classes, in beta, for the [browser use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-tool) and the [computer use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool). You subclass one and write one method per tool against your own browser or desktop automation. The SDK runs the tool loop, the URL and file policies you set for the browser, and your approval callback. See [Browser and computer use with the SDK toolsets](https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-sdk).
76* Claude Max and Team plans now include monthly API credits. To learn how to claim them, see [API credits for Max and Team plans](https://platform.claude.com/docs/en/about-claude/api-credits-for-subscribers).
76* Claude Max, Ultra, and Team plans now include monthly API credits. To learn how to claim them, see [API credits for Max, Ultra, and Team plans](https://platform.claude.com/docs/en/about-claude/api-credits-for-subscribers).
7777* In Claude Managed Agents, a cloud environment with `limited` networking now also applies its `allowed_hosts` to the `web_search` and `web_fetch` tools. A `web_fetch` call for a URL on a host that `allowed_hosts` does not match returns a `url_not_allowed` error result to the agent. `web_search` omits results from such hosts. When `allowed_hosts` lists no hosts, neither tool returns a page or a search result. `allow_package_managers` and `allow_mcp_servers` add no hosts for these tools. To let the tools reach a host, add it to `allowed_hosts`, which also opens it to the sandbox. `unrestricted` networking and self-hosted environments do not limit these tools. See [Environment networking](https://platform.claude.com/docs/en/managed-agents/environments#networking).
7878* With `limited` networking, creating a session fails with a 400 error when an enabled web tool’s `allowed_domains` has an entry not within `allowed_hosts`. So does a session update that adds such an entry. An `allowed_hosts` entry matches one exact host unless it starts with `*.`, so `docs.example.com` is not within `["example.com"]`. To fix the error, add the host to `allowed_hosts` or remove the entry from `allowed_domains`. See [Restrict web search and web fetch domains](https://platform.claude.com/docs/en/managed-agents/tools-web-restrictions).
7979* In Claude Managed Agents, the [`web_fetch` tool](https://platform.claude.com/docs/en/managed-agents/tools#available-tools) now fetches only URLs that have already appeared in the session, for example in the text of a user message, in a `web_search` result, or in a page that `web_fetch` returned earlier. This reduces the risk of data exfiltration. A URL that appears only in Claude’s own output, the agent’s system prompt, an attached document, or the output of a tool such as `bash`, `read`, or an MCP tool does not count: a `web_fetch` call for it returns a `url_not_in_prior_context` error result to the agent. To let the agent fetch a URL, send it in the text of a `user.message` event.
Feedback