Anthropic SDK
An official software development kit provided by Anthropic for building AI applications and agents based on Claude models. It encapsulates core capabilities including tool calling, multi-turn conversation management, and cost tracking, enabling developers to integrate Claude model functionality into their applications through a structured programmatic interface.
Core Facts
Timeline (last 90 days)
Anthropic is gradually pushing enterprise-level management capabilities down into the official SDK layer, reducing customers' duplicated work at the integration layer.
When upgrading to v2.3.0, integrations that use the Google Cloud path and are sensitive to the user profile request endpoint require additional verification.
When upgrading to v2.3.0, custom wrappers that depend on the specific query parameters sent by the SDK (especially beta-related parameters) require additional verification.
v2.3.0's workflow is changed to validate repositories by owner and public name, and the preview build upload step is removed from CI.
v2.3.0 removes a redundant await in the tool_runner async example.
v2.3.0 adds links to the SDK documentation in the docstrings of the raw responses for Bedrock and Vertex, and updates the README and example requests.
v2.3.0 rewrites the explanatory text for work queue, skill and external key.
v2.3.0 updates the documentation's description of the code execution tool and its encrypted results.
v2.3.0 internally switches to reading the beta route qualifier instead of relying on the beta=true query parameter; parse and stream no longer send the beta query parameter.
v2.3.0 stops hardcoding query parameters in endpoint paths and lifts query parameters carried in endpoint paths up to the request layer for unified handling.
40 more timeline events
All Facts (20)
TypeScript's static type checking can catch structural errors at compile time.
75%VerifiedThe Anthropic official SDK released version v1.12.1.
75%Unverifiedv2.3.0 internally switches to reading the beta route qualifier instead of relying on the beta=true query parameter; parse and stream no longer send the beta query parameter.
50%UnverifiedWhen upgrading to v2.3.0, custom wrappers that depend on the specific query parameters sent by the SDK (especially beta-related parameters) require additional verification.
50%UnverifiedWhen upgrading to v2.3.0, integrations that use the Google Cloud path and are sensitive to the user profile request endpoint require additional verification.
50%UnverifiedAnthropic is gradually pushing enterprise-level management capabilities down into the official SDK layer, reducing customers' duplicated work at the integration layer.
50%Unverifiedv2.3.0 stops hardcoding query parameters in endpoint paths and lifts query parameters carried in endpoint paths up to the request layer for unified handling.
50%UnverifiedThe release notes corrected the usage and cost report example and the documentation related to ending_at.
50%Unverifiedv2.2.0 added the ability to view usage and cost reports by dimension and marked the old reports as legacy.
50%UnverifiedWhen set_messages_params() does not provide betas, user_profile_id, and workspace_id, the tool runner retains the original values rather than clearing them.
50%UnverifiedThe tool runner's set_messages_params() callback no longer adds the current response to the params.
50%UnverifiedWhen set_messages_params() provides tools in definitions form, the tool runner continues to run its function tools; once a tool is removed from tools, the runner no longer executes it.
50%UnverifiedThe certifi version in the dev lockfile was bumped in v2.2.0.
50%UnverifiedThe error message for the client max_retries no longer suggests using math.inf.
50%UnverifiedThe documentation clarified the meaning of the plugin served_version_pinned and updated_at fields.
50%UnverifiedIn the tool runner, after append_messages() the history is now managed by the caller.
50%UnverifiedThe release notes clarified that the model list in rate limits varies by organization and workspace.
50%UnverifiedAt the API level, v2.2.0 introduced support for message threads.
50%UnverifiedFor projects already using the tool runner, the callback behavior changes in v2.2.0 (history attribution and dynamic removal of tools) are compatibility adjustments to watch out for, and regression testing of multi-turn tool-calling flows after upgrading is recommended.
50%UnverifiedThe only feature entry in the v2.1.0 changelog is: add enforcement status, actions and filter to user profiles.
50%