Tag: agentcore
All the articles with the tag "agentcore".
-
AgentCore Registry Is a Governed Catalog for Agent Interfaces
Hardcoded runtime ARNs are the visible pain, and Registry does fix them — but agent discovery is fundamentally a governance problem, not a routing problem.
-
An Agent That Can Pay for Its Tools
Payment is not a tool call—it is a governed financial action. An agent that pays requires user consent, credential isolation, session budgets, policy checks, and a proof path the model cannot bypass.
-
Harness vs. Runtime: When to Graduate
Harness gives you a working agent in 20 seconds with 25 lines of configuration. Runtime takes 398 lines of code. Both run on the same compute. The graduation trigger that matters is not hooks or custom loops — it's per-user outbound identity.
-
Build a Regression Suite for an Agent
I built a test suite for a support agent and found three classes of bugs that escape human review, output-quality scoring, and code review — and the regressions they taught me how to catch permanently.
-
Who May Call What: Per-User Authorization on AgentCore With Cedar
A valid token proves who is calling. AgentCore Policy is a Cedar engine on the gateway that answers who-may-call-what per user, per tool, per argument — default-deny, before the tool runs. I wired one up and watched it allow, then deny, the same call.
-
How AgentCore Gateway Turns Any API Into an Agent Tool
AgentCore Gateway is a managed front door between agents and tools. It handles inbound auth, outbound auth, and protocol translation once, so any API or Lambda becomes an MCP tool that every connected agent can call. Here is how the wiring actually works.