# Kam State documentation

Kam State adds versioned application state to Amazon Bedrock AgentCore.

Build an agentic app with AG-UI, Amazon Bedrock AgentCore, and Kam State. Start with the integration boundary, record one result, and read its exact retained revision.

> Use Kam State to retain the exact results and input references your AgentCore application needs beyond the current AG-UI interaction.

Status: Implemented in source. Prelaunch; not a live service guarantee.

Backend review: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs

## In short

AG-UI carries the interface interaction, Amazon Bedrock AgentCore hosts your agent, and Kam State keeps accepted results with exact revisions and recorded references. Start with one application-owned SDK integration. Record a result, inspect its retained version, and define the retry and changed-input behavior before adding more workflows.

**Available today:** Private SDK 0.49.0 is available for scoped evaluation; an authorized endpoint is required. Offline artifact evidence and the historical SDK 0.40.0 backend review do not establish a hosted or live-qualified AgentCore integration.

## Start with one agent workflow

1. **Understand the integration** — AG-UI carries interface events. AgentCore hosts your agent. Your backend explicitly records results and reads State through Kam.

2. **Record and retrieve one result** — Use the private SDK with an authorized endpoint. Keep the accepted ID and revision, then read that exact retained evidence.

3. **Exercise the failures** — Retry an identical record after a lost response, add a correction, and check unavailable evidence. Keep tool execution and external effects separate.

[AG-UI + AgentCore integration](/docs/ag-ui-agentcore)

[SDK quickstart](/developers#integration)

[Result-write retries](/docs/agent-result-retries)

## What Kam adds

Kam keeps the accepted revisions your application records, returns exact retained versions, and preserves fixed History membership. Supported retries return retained acceptance evidence. Declared Views and bounded State reconciliation build on that foundation.

[Exact History contract](/docs/history)

[State queries](/docs/state-api)

[Versioned Context](/docs/context)

## What your application owns

Your application owns domain meaning, authentication, model and tool execution, and external-action verification. AgentCore Memory provides separately configured recall. General collections, watch(), and managed runtime wiring remain planned.

## SDK access and evidence

The website bundles private SDK 0.49.0 (@kam-ai/agentcore-history-sdk). Its offline artifact verification is separate from the broader backend review pinned to SDK 0.40.0. Neither establishes a hosted service or live AgentCore qualification.

Obtain the approved artifact, endpoint, principal and tenant binding through an evaluation. Public documentation and examples need no credentials. There is no public npm release or one-click AgentCore attachment.

[Request evaluation access](/evaluation)

[Review qualification evidence](/docs/qualification)

## Plan what must remain inspectable

Working History covers a bounded window of 365 UTC dates. Supporting evidence has separate retention limits, and every read still needs authority. A missing exact version stays explicit.

[Retention contract](/docs/retention)