◈ AWS AGENTCORE BLUEPRINTS
PART III · TOOLS AND OPERATIONS · CHAPTER 22 / 36
TOCCONSULTING.FR
AMAZON BEDROCK / SERVICE DETAIL S09 EVALUATIONS

AGENTCORE EVALUATIONSPRACTICAL

CHAPTER 22 / 36
TOPIC add a grader, score your agent
REV 2026.07
IN PLAIN WORDS

You will add an automatic grader to your agent, run it on past conversations to get scores, and optionally let it grade new conversations as they happen. Terms: evaluator = the grader (a built-in one, or your own); on-demand = you run it now; online = it runs continuously; LLM-as-a-Judge = a model does the grading.

[ 1 ] PREREQUISITES
[x] An AgentCore agent with Observability on (it produces traces)
[x] AWS credentials, the AgentCore CLI
[x] Model access for the judge model (needed for custom evaluators; built-ins are fully managed)
[ 2 ] ADD A GRADER TO YOUR PROJECT
$ agentcore add evaluator # create a custom grader (built-ins are used by Builtin.* id, no add needed) $ agentcore deploy # apply it
[ 3 ] GRADE NOW, OR GRADE CONTINUOUSLY
ON-DEMAND before you ship
$ agentcore run eval # grade past runs now (e.g. --evaluator "Builtin.Helpfulness") $ agentcore evals history # view past results (agentcore logs evals to stream)
ONLINE after you ship
$ agentcore add online-eval # score new runs automatically $ agentcore deploy $ agentcore pause online-eval / resume online-eval # pause or resume it
[ 4 ] WHERE THE SCORES GO
Pick a built-in evaluator by id (for example Builtin.Helpfulness) or use a custom one. Scores appear in the CloudWatch GenAI Observability dashboard next to your traces, so you can chart quality over time and set an alarm when it drops. Online graders are managed as an "online evaluation configuration" (create, get, list, update, delete).
Tip: run an on-demand evaluation on every new version before release, then keep an online one running in production to catch regressions in real use.
SRC: AWS AgentCore Developer Guide (evaluations, built-in evaluators, online evaluation) + AgentCore CLI
DRAWN 2026.06, REV 2026.07.26
◄ PREVIOUS · CH 21
AgentCore Evaluations, Plain Language
NEXT · CH 23 ►
AgentCore Policy, Plain Language
AWS AGENTCORE BLUEPRINTS · CONTENTS
Back to tocconsulting.fr Cover & Table of Contents
PART I · FOUNDATIONS
01AgentCore Overview, Plain LanguageCONCEPT02AgentCore, Key Terms in Plain LanguageCONCEPT03AgentCore, Common Mistakes ExplainedCONCEPT04Inside an AgentCore Agent, BlueprintCONCEPT05Harness, Practical 1, Strands PathPRACTICAL06Harness, Practical 2, Managed HarnessPRACTICAL
PART II · CORE SERVICES
07AgentCore Runtime, Plain LanguageCONCEPT08AgentCore Runtime, PracticalPRACTICAL09AgentCore Memory, Plain LanguageCONCEPT10AgentCore Memory, PracticalPRACTICAL11AgentCore Gateway, Plain LanguageCONCEPT12AgentCore Gateway, PracticalPRACTICAL13AgentCore Identity, Plain LanguageCONCEPT14AgentCore Identity, PracticalPRACTICAL
PART III · TOOLS AND OPERATIONS
15AgentCore Code Interpreter, Plain LanguageCONCEPT16AgentCore Code Interpreter, PracticalPRACTICAL17AgentCore Browser, Plain LanguageCONCEPT18AgentCore Browser, PracticalPRACTICAL19AgentCore Observability, Plain LanguageCONCEPT20AgentCore Observability, PracticalPRACTICAL21AgentCore Evaluations, Plain LanguageCONCEPT22AgentCore Evaluations, PracticalPRACTICAL
PART IV · GOVERNANCE AND TRANSACTIONS
23AgentCore Policy, Plain LanguageCONCEPT24AgentCore Policy, PracticalPRACTICAL25AgentCore Registry, Plain LanguageCONCEPT26AgentCore Registry, PracticalPRACTICAL27AgentCore Payments, Plain LanguageCONCEPT28AgentCore Payments, PracticalPRACTICAL
PART V · MULTI-AGENT AND ARCHITECTURE
29A2A and Multi-Agent, Plain LanguageCONCEPT30A2A and Multi-Agent, PracticalPRACTICAL31Architecture Patterns, Plain LanguageCONCEPT32Multi-Tenant Agents, Plain LanguageCONCEPT33Agent Security and Threat Model, Plain LanguageCONCEPT34Governance at Org Scale, Plain LanguageCONCEPT35Governance at Org Scale, PracticalPRACTICAL36Multi-Region and Distribution, Plain LanguageCONCEPT