On October 28 Anthropic raised the first-party Messages and Token Counting HTTP body limit from 32 MB to 128 MB; on October 29 it launched the Usage and Cost Analytics API beta, which returns token and dollar rows as JSON. The 128 MB cap covers the whole request (prompt, history, base64 documents), not higher per-image or per-page limits. Analytics calls need anthropic-beta: analytics-usage-cost-2026-08-24, and you read each row’s group, usage, or cost, then paginate with next_page. The older Usage and Cost API and Enterprise report endpoints are now legacy but remain supported with migration guides.
This piece is written for 30 October 2026, from the October 28–29 release notes and Analytics documentation. Four days ago we covered API version 2026-10-21 and temperature 400 errors. That upgrade was about legal request fields; this one is about payload size and billing JSON shape.
Which endpoints get 128 MB
The release notes apply the change only to the first-party Claude API Messages and Token Counting endpoints. Message Batches stay at 256 MB; Files API at 500 MB; Sessions, Agents, and Environments traffic stays at 32 MB. You are buying headroom for large inline PDFs and histories, not a larger context window by itself.
| First-party endpoint | Before | After Oct 28 |
|---|---|---|
| Messages / Token Counting | 32 MB | 128 MB |
| Message Batches | 256 MB | 256 MB |
| Files API | 500 MB | 500 MB |
Per-image, per-page, and per-request image count limits still apply. Use Token Counting before you assume a file under 128 MB will pass.
Why Bedrock stays at 20 MB
Partner-hosted platforms keep their own ceilings. Typical documented values: Amazon Bedrock about 20 MB, Google Cloud (Google managed) about 30 MB, and several Anthropic-managed or Foundry paths about 32 MB. A pipeline tuned to 128 MB on the first-party API may still fail on Bedrock.
Store max_request_bytes per platform in config. Feature parity with Bedrock structured output does not imply the same transport limit.
How to call Analytics
GET /v1/organizations/analytics/usageGET /v1/organizations/analytics/cost
Send anthropic-version and anthropic-beta: analytics-usage-cost-2026-08-24. Query with time bounds, optional time_bucket_width=1d, and up to five group_by[] dimensions such as model or api_key_id. Follow next_page while has_more is true; note data_refreshed_at for freshness.
Adding usage row token fields
Each row has period bounds, a group object, and usage. Dimensions not listed in group_by[] appear as null in group; that is not zero usage.
{
"data": [{
"starting_at": "2026-09-03T00:00:00Z",
"ending_at": "2026-09-04T00:00:00Z",
"group": {"model": "claude-sonnet-5", "workspace_id": null},
"usage": {
"uncached_input_tokens": 1284500,
"cache_creation": {
"ephemeral_5m_input_tokens": 215300,
"ephemeral_1h_input_tokens": 0
},
"cache_read_input_tokens": 3200000,
"output_tokens": 891000,
"total_tokens": 5590800,
"requests": 4210
}
}],
"has_more": true,
"next_page": "page_...",
"data_refreshed_at": "2026-09-18T16:02:11Z"
}
Bill cache writes from the 5m and 1h buckets separately from cache reads. OpenAI Responses uses different field names such as ttl_30m_tokens; do not force them into one schema.
Reading cost amount
cost.amount is documented as post-discount, pre-credit fractional cents; list_amount is pre-discount. Currency is USD today. When grouping by cost_type or token_type, requests may be null; read request counts from an ungrouped row.
- JSON Validator
- JSONPath
- JSON Diff against legacy reports
What happens to legacy reports
October 29 marks the prior Usage and Cost API and Enterprise usage_report / cost_report family as legacy while keeping them online. New work should target Analytics; run parallel JSON diffs on the same window before you cut over.
FAQ
Can I base64 a 120 MB PDF into messages now?
Not automatically. Sub-limits on PDFs, images, and image counts still apply, plus JSON overhead. Use Token Counting first.
Did Message Batches move to 128 MB?
No. Batches remain at 256 MB.
What if the Analytics beta header is missing?
The beta endpoints will not work. Send analytics-usage-cost-2026-08-24.
Does null in group mean no data?
Usually it means the dimension was not grouped or has no value on that row. Check usage or cost metrics.
Is amount already in US dollars?
It is fractional cents per the docs. Convert carefully; do not treat the string as a dollar float.
Will legacy usage_report stop working?
Release notes say it remains supported. New dimensions and actor breakdowns land on Analytics.
Summary
October 28–29: bigger first-party bodies and richer billing JSON. Do not port 128 MB assumptions to Bedrock; paginate Analytics and respect cache subfields. Keep legacy feeds until diffs match.