Skip to main content

Evaluation / one focused workload

One workload. A State contract you agree on first.

For AgentCore teams whose agents keep rebuilding the same State: start with exact History and one bounded View, then define the metrics and views your agents should share, without building the whole subsystem yourself.

Design-partner conversation

Kam for AgentCore

Start with one workload where State changes while agents wait: customer health, deployment readiness, order exceptions, incident response, or another explicit domain.

Discuss an evaluation

Pricing and delivery terms are agreed after scope review. No public subscription or production commitment is offered on this page.

Proposed evaluation checklist

  1. Pin exact History

    Prove stable identity, exact retry behavior, corrections, generation-bound membership and exact byIds hydration.

  2. Exercise State change detection

    Define one bounded View, change one source, and verify affected State changes while unrelated retained evidence stays inspectable.

  3. Design the metrics and views

    Agree on the State your agents should share and the metrics derived from it. This shapes the planned State API; it does not activate one.

  4. Profile a turn locally

    Use the reviewed native candidate to compare reference-only Turn Frames and explain why State was rebuilt, blocked, or reusable—without claiming live model interception.

  5. Review live qualification gaps

    Deployment, IAM, buyer lifecycle, context payload custody, runtime hooks, performance and effect authorization remain explicit production gates.

AWS Marketplace is the planned purchasing channel. There is no live listing or one-click activation yet. An evaluation request opens an email conversation; it does not subscribe you, authorize AWS access, upload customer records, or activate live Turn interception.