# Claude API

In its Claude Platform release notes, Anthropic cut the price of prompt cache reads on Claude Sonnet 5.5 from $0.20 to $0.10 per million tokens, which is 0.05x the base input price instead of 0.1x. Cache writes and all other prices are unchanged. For developers who resend the same long prefix, the saving applies to re-reading the cache, not to the first write or to newly generated content.

In its Claude Platform release notes, Anthropic cut the price of prompt cache reads on Claude Sonnet 5.5 from $0.20 to $0.10 per million tokens, which is 0.05x the base input price instead of 0.1x. Cache writes and all other prices are unchanged. For developers who resend the same long prefix, the saving applies to re-reading the cache, not to the first write or to newly generated content.

Anthropic's Claude Platform release notes say a Claude Managed Agents agent can now use dynamic workflows for work with many pieces, such as reviewing hundreds of documents. A workflow is a program that runs many agents in phases and combines their results, and the server runs it in the background as a workflow run. The capability is in beta under the managed-agents-2026-04-01 beta header, enabled by setting the agent's multiagent field to type multiagent_20261001 with workflows enabled.

Anthropic's Claude Platform release notes say a Claude Managed Agents agent can now use dynamic workflows for work with many pieces, such as reviewing hundreds of documents. A workflow is a program that runs many agents in phases and combines their results, and the server runs it in the background as a workflow run. The capability is in beta under the managed-agents-2026-04-01 beta header, enabled by setting the agent's multiagent field to type multiagent_20261001 with workflows enabled.

Anthropic released message threads in beta on the Claude Platform Messages API, keeping the conversation on the server so later requests send only new messages, which makes requests smaller and lowers time to first token for long conversations and agent loops. The feature is enabled with the message-threads-2026-08-12 beta header, a thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

Anthropic released message threads in beta on the Claude Platform Messages API, keeping the conversation on the server so later requests send only new messages, which makes requests smaller and lowers time to first token for long conversations and agent loops. The feature is enabled with the message-threads-2026-08-12 beta header, a thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

Claude Platform now offers organizations an IP allowlist in the Claude Console, in beta. Previously a leaked API key could be used from any address to reach covered services; with the allowlist on, requests from addresses not on the list are refused, limiting where the key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

Claude Platform now offers organizations an IP allowlist in the Claude Console, in beta. Previously a leaked API key could be used from any address to reach covered services; with the allowlist on, requests from addresses not on the list are refused, limiting where the key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

Anthropic now offers an IP allowlist for organizations in the Claude Console, in beta, and requests to covered services from addresses not on the list are refused, which limits where a leaked API key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization. Previously an organization could not narrow the entry point for requests by source address in the console; this setting shrinks the usable range after a key leak from any address to the listed ones.

Anthropic now offers an IP allowlist for organizations in the Claude Console, in beta, and requests to covered services from addresses not on the list are refused, which limits where a leaked API key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization. Previously an organization could not narrow the entry point for requests by source address in the console; this setting shrinks the usable range after a key leak from any address to the listed ones.

Anthropic added a beta IP allowlist to the Claude Console, so only addresses on an organization's list can reach covered services, which limits where a leaked API key can still be used. Previously organizations had no console-level way to narrow requests by source address. Admins can enter IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

Anthropic added a beta IP allowlist to the Claude Console, so only addresses on an organization's list can reach covered services, which limits where a leaked API key can still be used. Previously organizations had no console-level way to narrow requests by source address. Admins can enter IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

Anthropic released message threads in beta for the Claude Messages API: the API keeps the conversation on the server, so each later request sends only the new messages, making requests smaller and lowering time to first token for long conversations and agent loops. Previously such workloads had to resend the full history each turn. A thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

Anthropic released message threads in beta for the Claude Messages API: the API keeps the conversation on the server, so each later request sends only the new messages, making requests smaller and lowering time to first token for long conversations and agent loops. Previously such workloads had to resend the full history each turn. A thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

Anthropic has released message threads in beta on the Messages API, keeping long conversations and agent loops on the server so each later request sends only the new messages, which the release notes describe as smaller requests and a lower time to first token. Previously such multi-turn calls had to resend the full history each time. The feature uses the message-threads-2026-08-12 beta header, a thread expires 5 minutes after its last request and is deleted no more than 1 hour after last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed) and Claude in Microsoft Foundry.

Anthropic has released message threads in beta on the Messages API, keeping long conversations and agent loops on the server so each later request sends only the new messages, which the release notes describe as smaller requests and a lower time to first token. Previously such multi-turn calls had to resend the full history each time. The feature uses the message-threads-2026-08-12 beta header, a thread expires 5 minutes after its last request and is deleted no more than 1 hour after last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed) and Claude in Microsoft Foundry.