Tag: agentcore
All the articles with the tag "agentcore".
-
Where AgentCore Sits in the Architecture
Updated:AgentCore is a governed server-side hub: Runtime hosts the agent, Gateway authorizes tool calls, and Identity hands token exchange to the provider.
-
The AgentCore Map: What Each Piece Actually Does
Updated:Amazon Bedrock AgentCore is not one service — it is a set of primitives you can use à la carte. Here is the map: what each piece does, which problem it solves, and how they compose, so the names stop blurring together.
-
MPP vs x402: Two Competing Answers to the Same HTTP 402
AgentCore Payments speaks both protocols natively. I tested x402's metered settlement and built a spec-compliant MPP challenge to compare what each actually buys: simplicity and on-chain audit trails versus multi-rail reach and high-frequency billing.
-
Building an Autonomous AI News Agent on Step Functions and AgentCore
A daily pipeline that fetches 24 RSS feeds, dedups across sources, categorizes into nine fixed buckets, tracks story threads across days, and writes a digest with no human in the loop. What broke, what the real timeout ceiling turned out to be, and why the shape changed twice before it worked.
-
Four Tools, One Loop: The AgentCore Knowledge Worker
An agent that only calls APIs hits a wall when the answer lives in a rendered page, a computation, or last month's session. I wired a four-tool loop inside an AgentCore Runtime — search, browser, Code Interpreter, Memory — and ran it live. The prescriptive prompt is the product surface; the infrastructure is fixed.
-
AgentCore Browser: A Managed, Isolated Browser an Agent Can Drive
Some tasks only exist on a screen. The reflex is to run Playwright on a box. AgentCore Browser is the managed alternative: a per-session, isolated Chromium you drive over CDP, with session isolation, live-view human takeover, and replay-to-S3 audit built in. Here's what the primitive is, how you reach it, and the ceiling it doesn't cross.
-
Beyond Semantic Retrieval: Metadata Filtering in Agent Memory
Semantic search finds things that sound related. Sometimes you need a WHERE clause instead — filter by priority, by date, by category. I tested metadata filtering in AgentCore Memory and found a quiet gate: custom keys silently drop unless declared as indexed keys. Here's what works and what decides whether any of it works at all.
-
Bedrock Managed Knowledge Bases as a Native Gateway Tool
AgentCore Gateway now ships a native bedrock-knowledge-bases connector that replaces the Lambda wrapper entirely. Attach the KB to the Gateway and it auto-exposes Retrieve and AgenticRetrieveStream over MCP. The constraint: it only works with Managed Knowledge Bases, not customer-managed ones.