Tag: bedrock
All the articles with the tag "bedrock".
-
Grok 4.6 Is on Amazon Bedrock. Here Is How to Wire Grok Build to It
SpaceXAI's Grok 4.6 is now on Amazon Bedrock. Connect Grok Build directly with an AWS profile, a short-lived credential helper, and three switchable model routes.
-
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.
-
A Browser That Pays
When a browser navigates to a paywall, it gets a different challenge shape than a script does. The managed Browser Tool handles it the same way: read the challenge, generate proof, retry.
-
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.
-
Every Way to Attribute Cost on Amazon Bedrock, Live-Tested
A working map of every mechanism Amazon Bedrock has for attributing inference cost — resource tags, identity tags, and request metadata — with config examples, and where SaaS billing has to leave the AWS billing layer entirely.
-
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.
-
What You Build on the AgentCore Harness
Once AgentCore is placed as a governed server-side hub, the question turns from what it lacks to what you assemble on it. Four use-case shapes teams are shipping in 2026 — agentic analytics, a research copilot, enterprise workflow automation, and support triage — each with the wiring behind it: a Bedrock model doing the reasoning, AgentCore holding the operational parts together.
-
Browser Use vs. AgentCore Browser: Two Managed Browsers, and Which Layer Each One Wins
AgentCore Browser gives an agent a governed browser inside your AWS account. Browser Use Cloud gives it a natural-language browser with a stealth moat. I ran eleven live experiments against Browser Use — extraction, structured output, profiles, deterministic rerun, MCP, human-in-the-loop, and a stealth benchmark — and put it head-to-head with AgentCore Browser on identical tasks. The interface, the cost, and the differentiator are not where the marketing points.