One of the main reasons enterprises choose Claude Platform on AWS over the first-party Claude API is procurement: there is no new vendor to onboard and no separate payment relationship to manage. Anthropic runs the models and the API surface, while AWS handles authentication, access control, and — the subject of this article — billing through AWS Marketplace. Understanding how the charge is metered, denominated, and invoiced will save your finance team a confused email at the end of the first month.
Claude Consumption Units: the billing currency
Usage on Claude Platform on AWS is not billed to AWS in raw tokens. It is denominated in Claude Consumption Units (CCUs) — a metering unit priced at $0.01 per CCU, so 100 CCUs equal $1.00 of fees at Anthropic's standard per-model rates, after any applicable discounts. Think of CCUs as a dollar-equivalent meter reading, not a product you buy: they are not prepaid credits, and you cannot stockpile them. Your applications consume tokens at the normal published model prices; the platform converts that spend into CCUs for the marketplace meter.
| Billing characteristic | How it works |
|---|---|
| Unit | Claude Consumption Units (CCUs), $0.01 each |
| Metering | Reported hourly to AWS Marketplace |
| Invoicing | Monthly, in arrears (postpaid only) |
| Where it appears | AWS Marketplace charges on your AWS invoice |
| Prepayment | Not available — CCUs are not credits |
Metering happens hourly and invoicing is monthly in arrears — you use the platform first and pay afterward, consolidated with the rest of your AWS spend. Because the charge arrives as an AWS Marketplace item, it can flow through your existing AWS payment terms and, depending on your agreement with AWS, may interact with broader cloud-spend commitments. Confirm those specifics with your AWS account team rather than assuming.
Reconciling the invoice against token usage
The Marketplace line item is a consolidated figure, so reconciliation means connecting it back to token-level activity. Your primary tool is the Claude Console (accessed via the "Open Claude Console" federation flow from the AWS Console): its Usage, Cost, Limits, and Workspaces pages read organization metadata directly from Anthropic and show consumption broken down for your organization. Usage, quotas, and cost all roll up per workspace, so a workspace-per-team structure gives you a natural breakdown to match against the invoice — see cost allocation for Claude Platform on AWS.
One important gap: the programmatic Usage and Cost API is not available on Claude Platform on AWS. On the first-party Claude API you could pull cost reports from an Admin endpoint; here, most Admin API endpoints (including usage and cost reports) are among the documented exceptions to the platform's otherwise same-day feature parity. Plan on the Console views plus AWS-side billing tooling (Cost Explorer, budgets) rather than an automated Anthropic-side export — see viewing costs in AWS Cost Explorer.
Spend controls live on the AWS side
Anthropic's Console spend limits are also not available on Claude Platform on AWS — the docs direct you to rely on AWS billing controls instead. Two practical consequences:
First, set up AWS Budgets alerts on your Marketplace spend early, because nothing on the Anthropic side will pause usage at a dollar threshold for you. Second, note that rate limits and quotas are managed by Anthropic, not by AWS quota systems: new organizations start on the Start usage tier and do not move up tiers automatically — you contact Anthropic to raise limits. Rate limits are your throughput ceiling; AWS billing tools are your spend visibility.
What this means for finance
Brief your finance team with three sentences: the Claude Platform charge appears as an AWS Marketplace item denominated in CCUs at a cent each; it is postpaid monthly with hourly metering behind it; and the token-level detail needed for chargebacks comes from the Claude Console per workspace, not from the invoice itself. With that framing, the first invoice is a reconciliation exercise rather than a surprise.
Where to go next
Continue with cost allocation tags and workspaces and Cost Explorer setup, or start from the Marketplace subscription walkthrough if you haven't subscribed yet.