# Amazon — Reducing token costs and latency in Amazon Bedrock AgentCore JSON workloads

- Company: Amazon (amazon.com)
- Announced: 2026-11-17T22:44:51+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/reducing-token-costs-and-latency-in-amazon-bedrock-agentcore-json-workloads/
- Record: https://forck.live/items/37639-reducing-token-costs-and-latency-in-amazon-bedrock-agentcore-json-workloads
- Subject: Bedrock / Nova

Amazon's guide documents three composable strategies used to build a production agent for Flightscape that handles 20 MB+ JSON payloads on Amazon Bedrock AgentCore. The Training Schedule Optimization agent verifies crew training schedule assignments against business rules, but with 40+ tools and megabyte-scale JSON inputs, average request latencies exceeded 15 seconds across most calls. Every tool call injected its full payload into the model context, inflating token counts and costs, and on larger datasets the context window filled up before the agent could finish reasoning. The first strategy moves heavy artifacts such as request JSON, response JSON and validation data to Amazon S3, so AgentCore memory persists only stable references. When a tool returns an oversized list or dictionary, the agent stores the full result in S3 and passes the model a compact summary with a handle, which the model can expand using get_result_page_tool(). Together, the optimizations reduced token consumption by up to 71% and cut average latency by up to 80% across benchmark runs on a representative 23 MB payload.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/reducing-token-costs-and-latency-in-amazon-bedrock-agentcore-json-workloads/:

> As enterprises build production agents with dozens of tools and large structured inputs, token consumption and latency become the primary blockers to a good user experience. When these agents process large JSON data, every additional tool invocation injects the full payload into the large language model (LLM) context window, causing token usage and response latency to spike. Over multi-turn conversations, this pressure compounds, driving up costs and degrading response quality. Effectively managing context-window pressure in agentic systems is key to reliability and responsiveness at scale. In this post, we share three composable strategies we used to build a production agent for Flightscape that handles 20 MB+ JSON payloads. You can apply them to reduce token costs, lower latency, and maintain full reasoning capability across extended sessions. Together, these optimizations reduced token consumption by up to 71% and cut average latency by up to 80% across our benchmark runs on a representative 23 MB payload.
> 
> Solution overview
> 
> Flightscape is an airline operations platform that helps airlines plan and manage their crews, flights, and operations.

---

Record: https://forck.live/items/37639-reducing-token-costs-and-latency-in-amazon-bedrock-agentcore-json-workloads
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
