Skip to content
Talk to Us

Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.

Alternatives to Amazon Bedrock AgentCore

Amazon Bedrock AgentCore

AWS platform for building, deploying, and operating AI agents

Summary

Amazon Bedrock AgentCore is an AWS platform for building, deploying, and operating agents, which AWS says works with any framework and foundation model.⁠Source 1 Its modular services include a serverless Runtime that hosts agents, Gateway, Identity, Policy, and AWS Agent Registry.⁠Source 1, Source 2, Source 3, Source 4, Source 5

By Blocks.ai teamLast checked

Where Amazon Bedrock AgentCore sits

Six layers of running AI agents at a company, and what Amazon Bedrock AgentCore’s own public sources say it covers. Each alternative below gets the same six layers as a strip.

Public sources · checked 2 October 2026
  • Offered

Amazon Bedrock AgentCore

  • Build agents: OfferedHarness managed agent loop⁠Source 1
  • Host and run agents: OfferedAgentCore Runtime⁠Source 1
  • Identity and access: OfferedAgentCore Identity workload identities⁠Source 3
  • Registry and governance: OfferedAWS Agent Registry with approvals⁠Source 5
  • Traffic between agents, tools, and models: OfferedAgentCore Gateway⁠Source 6
  • Agents across organizations: OfferedRegistry shared through AWS RAM⁠Source 7

How to read the strips

  1. 01Build agents
  2. 02Host and run agents
  3. 03Identity and access
  4. 04Registry and governance
  5. 05Traffic between agents, tools, and models
  6. 06Agents across organizations
  • Offered
  • Preview
  • You build it
  • Not included
  • Not publicly documented

Platforms to build and run agents

5 alternatives

The group Amazon Bedrock AgentCore sits in, so listed first.

  • CrewAI AMP

    Platform for deploying, monitoring, and scaling CrewAI crews and agents

    Where it sits⁠Source 8, Source 9, Source 10, Source 11, Source 12, Source 13

    1. Build agents: Offered, Crew Studio visual editor
    2. Host and run agents: Offered, Managed infrastructure for crews
    3. Identity and access: Offered, Per-deployment allow lists
    4. Registry and governance: Offered, Agent Repositories
    5. Traffic between agents, tools, and models: Offered, Custom MCP server connections
    6. Agents across organizations: Preview, Public A2A agents

    CrewAI’s platform to deploy, monitor, and scale crews and agents in production.⁠Source 9 Its Enterprise plan can run on CrewAI’s cloud, your own VPC, or your own infrastructure; AgentCore is a managed service in AWS Regions.⁠Source 1, Source 14, Source 15

    Amazon Bedrock AgentCore vs CrewAI AMP

  • Gemini Enterprise Agent Platform

    Google Cloud platform to build, deploy, govern, and optimize AI agents

    Where it sits⁠Source 16, Source 17, Source 18, Source 19

    1. Build agents: Offered, Agent Studio low-code canvas
    2. Host and run agents: Offered, Agent Runtime
    3. Identity and access: Offered, SPIFFE-based Agent Identity
    4. Registry and governance: Offered, Agent Registry
    5. Traffic between agents, tools, and models: Offered, Agent Gateway
    6. Agents across organizations: Offered, Gateway calls to outside agents

    Google Cloud’s platform to build, deploy, govern, and optimize agents.⁠Source 16, Source 20 Its Agent Registry operates at the Google Cloud project level.⁠Source 21 Agent Registry is free; skill scanning is billed from January 2027.⁠Source 22

    Amazon Bedrock AgentCore vs Gemini Enterprise Agent Platform

  • IBM watsonx Orchestrate

    Agent management platform to build, deploy, orchestrate, and govern AI agents

    Where it sits⁠Source 23, Source 24, Source 25, Source 26, Source 27

    1. Build agents: Offered, Visual builder and ADK
    2. Host and run agents: Offered, Agents run on watsonx Orchestrate
    3. Identity and access: Preview, Agent identity
    4. Registry and governance: Offered, Agentic Control Plane
    5. Traffic between agents, tools, and models: Offered, A2A calls to agent endpoints
    6. Agents across organizations: Offered, Partner A2A agents in catalog

    IBM calls it an agent management platform to build, deploy, orchestrate, and govern agents, as SaaS or on premises.⁠Source 28, Source 29 It is sold by plan; AgentCore bills by use.⁠Source 30, Source 31 IBM’s agent identity is in private preview.⁠Source 32

    Amazon Bedrock AgentCore vs IBM watsonx Orchestrate

  • LangSmith

    Platform for observing, evaluating, and deploying agents

    Where it sits⁠Source 33, Source 34, Source 35, Source 36, Source 37

    1. Build agents: Offered, Fleet agent builder
    2. Host and run agents: Offered, LangSmith Deployment runtime
    3. Identity and access: Offered, Fleet per-agent permissions
    4. Registry and governance: Offered, Centralized registry in Deployment
    5. Traffic between agents, tools, and models: Offered, Fleet forwards MCP tool calls
    6. Agents across organizations: Not publicly documented

    LangChain describes it as a platform for observing, evaluating, and deploying agents.⁠Source 38 It runs in LangChain’s cloud, or self-hosted or hybrid, on Enterprise; AgentCore is a managed service in AWS Regions.⁠Source 1, Source 15, Source 39, Source 40

    Amazon Bedrock AgentCore vs LangSmith

  • n8n

    Platform for AI agents and workflows you can see and control, built visually or with code

    Where it sits⁠Source 41, Source 42, Source 43, Source 44

    1. Build agents: Offered, LangChain-based AI Agent node
    2. Host and run agents: Offered, Your infrastructure or n8n’s
    3. Identity and access: Not publicly documented
    4. Registry and governance: Preview, Agents stored in projects
    5. Traffic between agents, tools, and models: Offered, MCP client for external tools
    6. Agents across organizations: Not publicly documented

    n8n says you build AI agents and workflows in it, visually or with code, on n8n Cloud or self-hosted.⁠Source 42, Source 45 Its Agents feature is in preview.⁠Source 43 AWS Agent Registry can list agents outside AWS.⁠Source 1

    Amazon Bedrock AgentCore vs n8n

Agent control planes

5 alternatives

  • Blocks.ai

    Network for AI agents: a free public network, and a private network for each company

    Where it sits⁠Source 46, Source 47, Source 48, Source 49, Source 50

    1. Build agents: Not included, Use LangChain or CrewAI
    2. Host and run agents: Not included, You run your agent
    3. Identity and access: Offered, Machine identity per agent
    4. Registry and governance: Offered, Private registry and Admin Console
    5. Traffic between agents, tools, and models: Offered, Private network for every agent
    6. Agents across organizations: Offered, Partners share only chosen agents

    Blocks.ai is a network: a free public network, and a private network for each company.⁠Source 49, Source 51 Blocks.ai doesn’t build or host agents.⁠Source 46, Source 47 On the Pro tier, partner companies can join as their own organizations.⁠Source 51, Source 52

    Blocks.ai vs Amazon Bedrock AgentCore

  • Microsoft Agent 365

    Microsoft 365 control plane to discover, manage, govern, and secure AI agents

    Where it sits⁠Source 53, Source 54, Source 55, Source 56, Source 57

    1. Build agents: Not included, Use your chosen framework
    2. Host and run agents: Not included, You host your agent
    3. Identity and access: Offered, Entra Agent ID
    4. Registry and governance: Offered, Agent registry in admin center
    5. Traffic between agents, tools, and models: Preview, Tooling Gateway for MCP servers
    6. Agents across organizations: Not publicly documented

    A Microsoft 365 control plane for agents built and run elsewhere, with agent identities in Microsoft Entra.⁠Source 53, Source 54, Source 55, Source 58 It is licensed per user; AgentCore is billed by use.⁠Source 31, Source 59

    Amazon Bedrock AgentCore vs Microsoft Agent 365

  • MuleSoft Agent Fabric

    Control plane for agents, MCP servers, and APIs across platforms

    Where it sits⁠Source 60

    1. Build agents: Offered, Agent brokers in Agent Script
    2. Host and run agents: Offered, Agent brokers on CloudHub 2.0
    3. Identity and access: Offered, Omni Gateway authentication and authorization
    4. Registry and governance: Offered, Agent Registry in Anypoint Exchange
    5. Traffic between agents, tools, and models: Offered, Omni Gateway in request path
    6. Agents across organizations: Not publicly documented

    A control plane for agents, MCP servers, and APIs across platforms.⁠Source 61 MuleSoft says it applies control to agents wherever they run, and its scanners pull agent metadata from AgentCore into one searchable registry.⁠Source 62

    Amazon Bedrock AgentCore vs MuleSoft Agent Fabric

  • ServiceNow AI Control Tower

    What ServiceNow calls a central hub to discover, secure, govern, observe, and measure AI

    Where it sits⁠Source 63, Source 64, Source 65

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Offered, Scoped OAuth tokens (community docs)
    4. Registry and governance: Offered, AI inventory tied to CMDB
    5. Traffic between agents, tools, and models: Offered, AI Gateway (community docs)
    6. Agents across organizations: Not publicly documented

    ServiceNow describes it as a central hub to discover, secure, govern, observe, and measure AI.⁠Source 64 Its connector for Amazon discovers AgentCore agents, and its kill switch can block them.⁠Source 66, Source 67

    Amazon Bedrock AgentCore vs ServiceNow AI Control Tower

  • Workday Agent System of Record

    Workday system of record to find, add, register, configure, monitor, and manage AI agents

    Where it sits⁠Source 68, Source 69, Source 70

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Offered, Agent System User per agent
    4. Registry and governance: Offered, Agent Registry in Management Hub
    5. Traffic between agents, tools, and models: Offered, Agent Gateway for Workday APIs
    6. Agents across organizations: Not publicly documented

    A functional area you set up in each Workday tenant to register, configure, monitor, and manage agents, each with a unique Workday identity.⁠Source 68, Source 69, Source 71 Workday security policies and groups govern what each agent can access.⁠Source 72

    Amazon Bedrock AgentCore vs Workday Agent System of Record

Gateways, identity, and security

4 alternatives

  • Cloudflare MCP server portals

    Cloudflare One feature that puts MCP servers behind one governed endpoint

    Where it sits⁠Source 73

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Offered, Identity provider or service token
    4. Registry and governance: Offered, Centrally managed MCP servers
    5. Traffic between agents, tools, and models: Offered, Proxy for MCP tool calls
    6. Agents across organizations: Not publicly documented

    A portal that puts multiple MCP servers behind one HTTP endpoint, governed through Cloudflare Access.⁠Source 73, Source 74 A portal lists MCP servers; AgentCore can host agents and catalogs agents as well as tools.⁠Source 1, Source 5, Source 73

    Amazon Bedrock AgentCore vs Cloudflare MCP server portals

  • Kong AI Gateway

    Gateway that governs LLM, MCP, and agent-to-agent traffic

    Where it sits⁠Source 75, Source 76, Source 77

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Offered, Per-agent allow or deny lists
    4. Registry and governance: Preview, Konnect Catalog agents
    5. Traffic between agents, tools, and models: Offered, Gateway for LLM, MCP, A2A
    6. Agents across organizations: Not publicly documented

    A gateway for LLM, MCP, and A2A traffic, proxying to agents at their own URLs; in version 2.x, you run its data plane nodes.⁠Source 75, Source 78 Kong’s docs describe reaching AgentCore Runtime agents with SigV4-signed requests.⁠Source 75

    Amazon Bedrock AgentCore vs Kong AI Gateway

  • Okta for AI Agents

    Okta offering that gives AI agents a first-class identity so organizations can discover, onboard, protect, and govern them

    Where it sits⁠Source 79, Source 80, Source 81

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Offered, Agent identity and credentials
    4. Registry and governance: Offered, Universal Directory with human owners
    5. Traffic between agents, tools, and models: Preview, Agent Gateway for MCP tools
    6. Agents across organizations: Not publicly documented

    Okta says it gives AI agents a first-class identity.⁠Source 82 Agents built in-house or elsewhere are registered in an Okta org, and admins define what each can access.⁠Source 83, Source 84 Okta can import Amazon Bedrock AgentCore agents.⁠Source 85

    Amazon Bedrock AgentCore vs Okta for AI Agents

  • Zenity AI Agent Security & Governance Platform

    Security and governance platform for AI agents, aimed at security teams

    Where it sits⁠Source 86, Source 87

    1. Build agents: Not publicly documented
    2. Host and run agents: Not publicly documented
    3. Identity and access: Not publicly documented
    4. Registry and governance: Offered, AI Observability agent inventory
    5. Traffic between agents, tools, and models: Offered, Tool-call blocking for coding agents
    6. Agents across organizations: Not publicly documented

    A security and governance platform for AI agents.⁠Source 88 Zenity says it discovers agents, including inside Copilot Studio and Agentforce, and can block some actions in real time.⁠Source 86, Source 89 It describes how it secures agents in AgentCore.⁠Source 90, Source 91

    Amazon Bedrock AgentCore vs Zenity

Build it yourself

1 alternative

Not a product: your own team assembles the pieces.

  • Build it yourself (DIY)

    Building agent connections and controls in-house from open protocols, existing infrastructure, and open-source tools

    Where it sits⁠Source 92, Source 93, Source 94, Source 95, Source 96, Source 97

    1. Build agents: You build it, Open-source frameworks like ADK
    2. Host and run agents: You build it, Self-hosted, like LangGraph
    3. Identity and access: You build it, Your own identity provider
    4. Registry and governance: You build it, Your own agent registry
    5. Traffic between agents, tools, and models: You build it, Your gateway and service mesh
    6. Agents across organizations: You build it, A2A with API management

    Your teams connect and govern agents themselves, on open protocols such as A2A and MCP that leave authorization logic to the implementer.⁠Source 98, Source 99, Source 100 A2A’s docs say a curated registry means deploying and maintaining a registry service.⁠Source 95

    Amazon Bedrock AgentCore vs DIY

Questions buyers ask

Does Amazon Bedrock AgentCore keep a registry of every agent?

AWS Agent Registry, generally available since August 2026, catalogs agents, MCP servers, tools, and skills, including ones on premises or in other clouds, behind an approval workflow.⁠Source 1, Source 5, Source 101 With AWS Organizations, it currently auto-detects only AgentCore Runtimes and Gateways; other agents are published as records.⁠Source 102, Source 103

How is Amazon Bedrock AgentCore priced?

By use, with no upfront commitment or minimum fee; you pay only for what you use.⁠Source 31 AWS Agent Registry’s first 5,000 records a month are free, then $0.400 per 1,000 records.⁠Source 31 Runtime is billed per vCPU-hour and GB-hour.⁠Source 31

Can Amazon Bedrock AgentCore manage agents built elsewhere?

AgentCore Runtime works with frameworks such as CrewAI, LangGraph, and Google ADK.⁠Source 1 For agents hosted elsewhere, AWS says its Registry works with agents on premises or in other clouds, and Identity covers self-hosted ones.⁠Source 1, Source 104 Observability can show their metrics after extra setup.⁠Source 105

How we compare

Read the full method

Every claim on this page links to a public source. Where none answers a question, the page says so.

We re-check every fact at least every 90 days. This page was last checked .

Something wrong or out of date? Tell us and we’ll correct it.

Sources

107 public sources, each with the date we checked it. Every one opens in a new tab.

  1. Source 1: Overview - Amazon Bedrock AgentCore (Developer Guide) AWS · checked Back:abcdefghijk

  2. Source 2: Amazon Bedrock AgentCore Gateway: A secure AI gateway for agents, tools, and models AWS · checked Back to text

  3. Source 3: Provide identity and credential management for agent applications with Amazon Bedrock AgentCore Identity AWS · checked Back:ab

  4. Source 4: Policy in Amazon Bedrock AgentCore: Control Agent Interactions AWS · checked Back to text

  5. Source 5: AWS Agent Registry: Discover and manage agents, tools, and resources AWS · checked Back:abcd

  6. Source 6: HTTP passthrough targets - AgentCore Gateway AWS · checked Back to text

  7. Source 7: Sharing a registry across accounts with AWS RAM AWS · checked Back to text

  8. Source 8: Crew Studio CrewAI · checked Back to text

  9. Source 9: CrewAI AMP (platform docs introduction) CrewAI · checked Back:ab

  10. Source 10: Role-Based Access Control (RBAC) CrewAI · checked Back to text

  11. Source 11: Agent Repositories CrewAI · checked Back to text

  12. Source 12: Custom MCP Servers CrewAI · checked Back to text

  13. Source 13: A2A on AMP CrewAI · checked Back to text

  14. Source 14: Pricing | CrewAI CrewAI · checked Back to text

  15. Source 15: Amazon Bedrock AgentCore FAQs AWS · checked Back:ab

  16. Source 16: Agent Platform overview Google · checked Back:ab

  17. Source 17: Agent Gateway overview Google · checked Back to text

  18. Source 18: Agent Identity overview Google · checked Back to text

  19. Source 19: Agent Registry overview Google · checked Back to text

  20. Source 20: Gemini Enterprise Agent Platform (formerly Vertex AI) Google · checked Back to text

  21. Source 21: Set up Agent Registry Google · checked Back to text

  22. Source 22: Agent Registry pricing Google · checked Back to text

  23. Source 23: AI Agent Builder | IBM watsonx Orchestrate IBM · checked Back to text

  24. Source 24: Welcome to IBM watsonx Orchestrate Agent Development Kit IBM · checked Back to text

  25. Source 25: Agent identity overview IBM · checked Back to text

  26. Source 26: AI Agent Control Plane | IBM watsonx Orchestrate IBM · checked Back to text

  27. Source 27: Partner A2A (Agent2Agent) agents IBM · checked Back to text

  28. Source 28: IBM watsonx Orchestrate IBM · checked Back to text

  29. Source 29: Regional availability and outbound IP addresses IBM · checked Back to text

  30. Source 30: IBM watsonx Orchestrate Pricing IBM · checked Back to text

  31. Source 31: Amazon Bedrock AgentCore Pricing AWS · checked Back:abcde

  32. Source 32: Prerequisites for configuring agent identity IBM · checked Back to text

  33. Source 33: No-code agents with LangSmith Fleet LangChain · checked Back to text

  34. Source 34: LangSmith Deployment LangChain · checked Back to text

  35. Source 35: Agent platform comparison LangChain · checked Back to text

  36. Source 36: LangSmith Deployment LangChain · checked Back to text

  37. Source 37: Remote MCP servers LangChain · checked Back to text

  38. Source 38: LangSmith: The Agent Engineering Platform LangChain · checked Back to text

  39. Source 39: Cloud (SaaS) LangChain · checked Back to text

  40. Source 40: LangSmith Plans and Pricing LangChain · checked Back to text

  41. Source 41: LangChain in n8n n8n · checked Back to text

  42. Source 42: AI Workflow Automation Platform - n8n n8n · checked Back:ab

  43. Source 43: Build and manage agents n8n · checked Back:ab

  44. Source 44: MCP Client Tool n8n · checked Back to text

  45. Source 45: Choose how to use n8n n8n · checked Back to text

  46. Source 46: Why Blocks? Blocks.ai · checked Back:ab

  47. Source 47: What is Blocks? Blocks.ai · checked Back:ab

  48. Source 48: Authentication reference Blocks.ai · checked Back to text

  49. Source 49: Your company's private network Blocks.ai · checked Back:abcd

  50. Source 50: Joining a Blocks network Blocks.ai · checked Back to text

  51. Source 51: Pricing Blocks.ai · checked Back:ab

  52. Source 52: Solutions: Partner networks Blocks.ai · checked Back to text

  53. Source 53: Agent 365 SDK frequently asked questions | Microsoft Learn Microsoft · checked Back:ab

  54. Source 54: Microsoft Agent 365 SDK overview | Microsoft Learn Microsoft · checked Back:ab

  55. Source 55: Agent 365 identity | Microsoft Learn Microsoft · checked Back:ab

  56. Source 56: Agent Registry in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back to text

  57. Source 57: Bring your own (BYO) MCP server in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back to text

  58. Source 58: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Microsoft · checked Back to text

  59. Source 59: Licensing Documents Microsoft · checked Back to text

  60. Source 60: Agent Fabric Overview Salesforce · checked Back to text

  61. Source 61: Get Started with Agent Fabric Salesforce · checked Back to text

  62. Source 62: See Every Agent. Govern Every Agent. Control AI Costs. (mulesoft.com home page) Salesforce · checked Back to text

  63. Source 63: What's new in AI Gateway v3.4 - September 2026 release (ServiceNow Community, AI Control Tower articles) ServiceNow · checked Back to text

  64. Source 64: AI Control Tower - ServiceNow (product page) ServiceNow · checked Back:ab

  65. Source 65: AI Gateway Implementation Guide (ServiceNow Community, AI Control Tower articles) ServiceNow · checked Back to text

  66. Source 66: AI Service Graph Connector for Amazon release notes (ServiceNow Store version history) ServiceNow · checked Back to text

  67. Source 67: Control enforcement points (ServiceNow product documentation, Australia release) ServiceNow · checked Back to text

  68. Source 68: Concept: Agent Security (Workday Administrator Guide) Workday · checked Back:ab

  69. Source 69: About Workday Agents (Workday Administrator Guide) Workday · checked Back:ab

  70. Source 70: Concept: Workday Agent Gateway (Workday Administrator Guide) Workday · checked Back to text

  71. Source 71: Set Up Agent System of Record (Workday Administrator Guide) Workday · checked Back to text

  72. Source 72: Setup Considerations: Agent Security (Workday Administrator Guide) Workday · checked Back to text

  73. Source 73: MCP server portals · Cloudflare One docs Cloudflare · checked Back:abc

  74. Source 74: MCP governance · Cloudflare Agents docs Cloudflare · checked Back to text

  75. Source 75: AI Agents - Kong AI Gateway docs Kong · checked Back:abc

  76. Source 76: Agents in Catalog - Kong Docs Kong · checked Back to text

  77. Source 77: Kong AI Gateway product page Kong · checked Back to text

  78. Source 78: AI Gateway architecture - Kong Docs Kong · checked Back to text

  79. Source 79: Add AI agents manually (Okta Help Center) Okta · checked Back to text

  80. Source 80: Okta for AI Agents (product page) Okta · checked Back to text

  81. Source 81: Agent Gateway (Okta Help Center) Okta · checked Back to text

  82. Source 82: Okta brings first-class identity to AI agents with Agent SSO Okta · checked Back to text

  83. Source 83: Add and register AI agents (Okta Help Center) Okta · checked Back to text

  84. Source 84: AI agent resource connections (Okta Help Center) Okta · checked Back to text

  85. Source 85: Apps that support AI agent imports (Okta Help Center) Okta · checked Back to text

  86. Source 86: AI Observability | See Every Agent, Know What it Touches | Zenity Zenity · checked Back:ab

  87. Source 87: Coding and Personal Agents | Zenity Zenity · checked Back to text

  88. Source 88: AWS Marketplace: Zenity Zenity · checked Back to text

  89. Source 89: Runtime Boundaries | The Runtime Boundary for Autonomous AI | Zenity Zenity · checked Back to text

  90. Source 90: Amazon Bedrock AgentCore Security | Full-Lifecycle Control Zenity · checked Back to text

  91. Source 91: Inside the Agent Stack: Securing Agents in Amazon Bedrock AgentCore Zenity · checked Back to text

  92. Source 92: google/adk-python README (GitHub) github.com · checked Back to text

  93. Source 93: langchain-ai/langgraph README (GitHub) github.com · checked Back to text

  94. Source 94: Integrating with Model Context Protocol (MCP) - Keycloak keycloak.org · checked Back to text

  95. Source 95: Agent Discovery - A2A Protocol a2a-protocol.org · checked Back:ab

  96. Source 96: Designing MCP Gateway Uber's MCP Management Platform - Uber Blog uber.com · checked Back to text

  97. Source 97: Enterprise Features - A2A Protocol a2a-protocol.org · checked Back to text

  98. Source 98: Agent2Agent (A2A) Protocol Specification a2a-protocol.org · checked Back to text

  99. Source 99: modelcontextprotocol/modelcontextprotocol LICENSE (GitHub) github.com · checked Back to text

  100. Source 100: Specification - Model Context Protocol 2026-07-28 modelcontextprotocol.io · checked Back to text

  101. Source 101: Release notes - Amazon Bedrock AgentCore AWS · checked Back to text

  102. Source 102: Key capabilities - AWS Agent Registry AWS · checked Back to text

  103. Source 103: Concepts and terminology - AWS Agent Registry AWS · checked Back to text

  104. Source 104: Features of AgentCore Identity AWS · checked Back to text

  105. Source 105: Add observability to your Amazon Bedrock AgentCore resources AWS · checked Back to text

  106. Source 106: Network requirements Blocks.ai · checked Back to text

  107. Source 107: Solutions: Agent sprawl Blocks.ai · checked Back to text