Terms of Service Change History

Added comprehensive new section "Can customers offer Claude Code in their products?" that prohibits modifying the Claude Code binary, removes authentication methods, or reselling Claude usage on end users' behalf. Customers may only offer Claude Code if end users authenticate with their own credentials and usage is billed directly to them. This materially restricts how businesses can integrate and monetize Claude Code.

Effective: September 6, 2026

Expanded authentication section now explicitly prohibits developers from collecting, storing, or intermediating Claude.ai credentials or session tokens. Added clarification that sign-in to Claude accounts must complete through Anthropic's own flow. This creates stricter controls over how third-party developers can handle user authentication and credentials.

Effective: September 6, 2026

Added explicit restrictions on using Claude Code or Anthropic names/logos in product names, features, company names, or logos. Customers can only state in plain text that their product has Claude Code preinstalled. This prevents misrepresentation of affiliation or endorsement by Anthropic.

Effective: September 6, 2026

Healthcare BAA language was simplified and clarified. Removed the phrase "wants to use Claude Code" and "if the customer has executed a BAA" to make the requirement that BAA automatically extends to Claude Code API traffic when ZDR is enabled. This reduces ambiguity about BAA coverage scope.

Effective: September 6, 2026