clauding.de
DE

Enterprise & Security

Claude Admin API: Analytics, Spend Limits and RBAC Leave Beta in the SDKs

2 min read AI-generated

The usage and cost endpoints from the October 29 beta stay exactly where they were. Two new session error types for agents come along with the release.

Featured image for "Claude Admin API: Analytics, Spend Limits and RBAC Leave Beta in the SDKs"

Anthropic shipped Python SDK 2.4.0 and TypeScript SDK 1.4.0 on November 2, along with new releases of the Bedrock, Vertex, Microsoft Foundry and Google Cloud packages. The first line of the release notes: GA methods for analytics, spend limits and RBAC.

What api.md says

I checked api.md in the Python SDK, and it is unambiguous. These endpoints now exist without beta:

  • client.organization.analytics.*: summaries, users, apps.chat.projects, connectors, plugins, skills and artifacts
  • client.organization.spend_limits.*: including effective and the increase_requests with approve and deny
  • client.organization.rbac_groups.*: create, read, update, delete, manage members
  • client.organization.rbac_roles.*: read roles and their permissions

The beta paths under client.beta.organization.* remain in place. Nothing forces you to migrate today, but there is now a path that needs no beta header.

Usage and cost stay in beta

Here it gets more precise than the release line suggests. analytics/usage and analytics/cost still live only under client.beta.organization.*. Those are exactly the two endpoints from the Usage and Cost Analytics API that Anthropic put into beta on October 29. The older report endpoints have been legacy since the same day and also sit in the beta branch.

So what went GA is the analytics for Claude apps usage, not the billing side. That is a real difference. If you pull tokens and cost through the API, you stay on the analytics-usage-cost-2026-08-24 beta header.

Two new error types for agents

A side note that matters to anyone building agents: the SDKs now carry two new session error types, tool_use_limit_reached_error and compaction_limit_reached_error. Alongside them are types for analytics group_by and spend limit period filters, a user_profile_id on External Keys and Workspaces, and one fix: spend_limit may be null in the response to an approved increase request.

The SDK is the earlier indicator

The Claude Platform release notes do not mention the GA step yet; their newest entry from November 2 is about message threads. That is not a complaint, it is a pattern. The SDKs pick up new API surface regularly before the release notes describe it.

In practice: if you want to know what gets documented on the platform next, read the SDK releases. And read api.md with them—that was the only place saying today that half of the GA announcement is still sitting in the beta branch.

Sources

Claude PlatformAdmin APISDKEnterprise