Tag: agents
All the articles with the tag "agents".
-
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.
-
One Coding Agent, Three Bedrock APIs: Wiring OpenCode to Claude, GPT, Grok, and Kimi
A tested OpenCode configuration for running Claude, OpenAI GPT, xAI Grok, and Moonshot Kimi through their native Amazon Bedrock Runtime APIs.
-
Jev Does Not Write. That Is the Point.
TypeSafe's Jev returns a typed answer and a probability, not a paragraph. That is worth putting first on a clean enum, and worth nothing on a dirty one.
-
What Actually Differs Across Search APIs Built for Agents
Updated:Exa, Parallel, Perplexity, and AgentCore span raw retrieval, generated answers, managed research, and monitoring. Comparing them starts with separating those layers.
-
Search for Agents Is Becoming Its Own Market
Updated:Four search APIs built for AI agents don't agree on a winner — and their funding, product surfaces, and billing units define an infrastructure market, not a feature comparison.
-
A 200 Response Does Not Prove Search Worked
HTTP success proves transport. A credible agent-search evaluation separately tests the contract, evidence, tool calls, lifecycle cleanup, and cost.
-
Search Is a Pipeline, Not a Tool
Agent search works as a five-stage pipeline: discovery, extraction, verification, synthesis, and monitoring. Treating it as one tool hides the failures that matter.
-
Web Search as a Managed Connector: Wiring Amazon Bedrock AgentCore WebSearch Into Any Agent
Updated:Amazon Bedrock AgentCore WebSearch is a managed MCP connector backed by an Amazon-operated index, authorized through IAM, and priced at $7 per 1,000 queries.