Workspaces
Workspaces provide cost attribution for the Anthropic-compatible Messages API on the bedrock-mantle endpoint. Workspaces are the same underlying resource as projects and are managed using the Amazon Bedrock Projects API. When you tag a workspace, the tags flow to AWS Cost Explorer and AWS Cost and Usage Reports (CUR 2.0), so you can filter and group Amazon Bedrock spend by application, team, environment, cost center, or any other dimension.
For cost attribution using the Responses or Chat Completions APIs on bedrock-mantle, see Projects. For cost attribution on bedrock-runtime APIs, see Application inference profiles.
How cost attribution works
You reference a workspace in a Messages API request by setting the anthropic-workspace HTTP header. Tags applied to the workspace are attached to the billing record for each request and appear as AWS cost allocation tags in CUR and Cost Explorer.
For details on creating workspaces, managing tags, and using the Messages API with workspaces, see Workspaces (Anthropic-compatible).
Viewing workspace costs
After tagging your workspaces, activate the tags as cost allocation tags in the AWS Billing and Cost Management console:
Open the AWS Billing and Cost Management console.
In the navigation pane, choose Cost allocation tags.
Select the tags you applied to your workspaces.
Choose Activate.
Tags can take up to 24 hours to appear in Cost Explorer and CUR after activation. Cost allocation tags are not retroactive — only costs incurred after activation are tagged. For more information, see Activating user-defined cost allocation tags.
After tag activation, you can analyze Amazon Bedrock costs by workspace in the following tools:
-
AWS Cost Explorer – Filter by workspace tags to view cost trends over time. Group by tag to compare costs across workspaces.
-
AWS Cost and Usage Reports (CUR 2.0) – Query CUR data for line-item cost breakdowns by workspace tag.
