How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway
What happened
MoEngage explains how it used Amazon Bedrock AgentCore Gateway to expose roughly 400 private API operations as permission-scoped tools for 10 internal agents across seven AWS Regions. The architecture combines OpenAPI specifications, server-side Cedar policies, private connectivity, and semantic tool discovery while keeping identity out of model-visible arguments. MoEngage estimates it saved approximately six months of engineering effort and reduced API onboarding from days to hours.
Why it matters
MoEngage’s separation of API ownership from protocol, policy, and connectivity offers a reusable architecture for exposing internal services to agents while keeping identity and tool access under server-side control.
Read next
See the full storyMoEngage turns roughly 400 private API operations into agent tools with Amazon Bedrock AgentCore GatewayThe story so far
MoEngage used Amazon Bedrock AgentCore Gateway to make roughly 400 private API operations available as permission-scoped tools for 10 internal agents across seven AWS Regions. MoEngage estimates the approach saved approximately six months of engineering effort and cut the time to onboard APIs from days to hours. The architecture uses OpenAPI specifications to define operations, server-side Cedar policies to enforce permissions, private connectivity to reach APIs, and semantic discovery to help agents find tools. It also keeps identity information out of the arguments visible to the models.
Keep up with AI, one email a day
Model releases, price changes and compute developments, with original sources. Free, confirmed by email, and easy to unsubscribe. Read a past issue · 2026-10-29