Anthropic SDK for TypeScript 0.123

Apply the Node.js 24 and TypeScript 7 prompts first. These rules cover @anthropic-ai/sdk 0.123 clients, Messages, tools, streams, files, webhooks, beta resources, and organization administration.

Clients, credentials, and endpoints

• Construct Anthropic only in trusted server or worker code. Do not set dangerouslyAllowBrowser: true with an API key or other reusable credential.
• Select one authentication mechanism deliberately. API-key strings and authToken values, including environment defaults, take precedence over credentials and config; set apiKey: null and authToken: null when selecting those providers. Automatic resolution can read environment variables and local profile/config files.
• Treat credential-file locations, profile names, resolved base_url values, and configuration contents as deployment policy. Require restrictive ownership and permissions, and separately allowlist the HTTPS API and token-exchange origins: a profile's base_url can select the token endpoint even when baseURL overrides the API host.
• Keep baseURL, defaultHeaders, per-request headers, defaultQuery, custom fetch, fetchOptions, and middleware out of request-controlled data; each can redirect requests, inject authorization context, or observe secrets and content.
• Use separate credentials, organization/workspace scope, quotas, and spend limits per environment and tenant boundary. Never reuse an organization administration credential for ordinary Messages calls.
• Bind anthropic-workspace-id and anthropic-user-profile-id to the authorized tenant