Clarification of Claude API Monthly Spend Caps and Error Handling

The updated documentation on Claude API rate limits provides more precise information regarding monthly spend caps and the corresponding error handling. It clarifies that each tier (Start, Build, Scale) has a system-defined monthly spend cap, and exceeding this cap results in an HTTP 429 error with a `rate_limit_error` type and an `enforced_spend_limit_reached` error code. This error does not include a `retry-after` header, meaning retries will fail until the cap resets at the start of the next month or a higher limit is requested. For user-defined spend limits, reaching the cap now returns an HTTP 400 error with an `invalid_request_error` type, indicating a user-specified limit has been hit. The page also mentions that the Claude Platform on AWS follows similar monthly spend caps, though billing and tier increases function differently. New sections on 'Files', 'Skills', 'RBAC Groups', and 'RBAC Roles' have been added, though their specific connection to rate limits is not detailed within these provided lines. The previous content was less explicit about the distinct error messages and types when spend limits were reached.