Understand this story
On November 18, 2026, the AWS team published a post sharing three composable strategies for reducing the cost of JSON workloads on Amazon Bedrock AgentCore. According to an article published by AWS Machine Learning, these strategies target Flightscape's crew scheduling agent and, in benchmarks with 23 MB JSON payloads, cut token consumption by up to 71% and average latency by up to 80%. The specific approaches include: storing large JSON in Amazon S3 and keeping only content-addressed references in AgentCore memory; switching to paginated handles when tools return very large lists; and returning structural descriptors for very large dictionaries. Across 100 sample questions, total tokens dropped from 23.6 M to 8.5 M, and average trace latency fell from 7,930 ms to 2,461 ms. This share is currently the only disclosed progress.
AI-generated from public reports
Latest development · Report
AWS shares how to reduce JSON workloads on Amazon Bedrock AgentCore…Developments
1 confirmed developments
AWS shares cost- and latency-reduction strategies for AgentCore JSON workloads
Source:AWS Machine Learning
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Nov 18
AWS Machine LearningFirst-party
AWS shares how to reduce JSON workloads on Amazon Bedrock AgentCore…
The AWS team presented three composable strategies for Flightscape's crew scheduling agent, reducing token consumption by up to 71% and average latency by up to 80% in benchmarks with a 23 MB JSON payload. The approach is to store large JSON in Amazon S3, keep only content-addressed references in AgentCore memory, switch to paginated handles when tools return oversized lists, and return structural descriptors for oversized dictionaries. On 100 sample questions, total tokens dropped from 23.6 M to 8.5 M, and average trace latency dropped from 7,930 ms to 2,461 ms.
AI Trends