MoEngage exposes 400 internal APIs as agent tools via AgentCore Gateway
Overview
MoEngage used Amazon Bedrock AgentCore Gateway to expose about 400 private internal REST APIs as permission-scoped agent tools, according to an AWS Machine Learning Blog post.
The gateway serves roughly 400 registered API operations to 10 internal agents, and access is controlled by Cedar policies evaluated before tool lists are returned.
According to the post, the setup uses OpenAPI specs and VPC endpoints with no public endpoint, and avoids running a separate MCP server for each team. MoEngage says it saved an estimated six months of engineering effort and reduced onboarding a new API from days to hours. AgentCore feature availability varies by Region.
Written by AI from the articles below · updated Oct 29, 1:21 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- AWS Machine Learning BlogOfficialPickMoEngage turns 400 private APIs into agent tools with AgentCore Gateway
AIMoEngage used Amazon Bedrock AgentCore Gateway to expose about 400 private internal REST APIs as permission-scoped agent tools. The setup uses OpenAPI specs, Cedar policies evaluated before tool lists are returned, and VPC endpoints, with no public endpoint and no per-team MCP servers. The post says this saved an estimated six months of engineering effort and cut onboarding a new API from days to hours.
Heat Trend
Not enough continuous observations to show a trend yet.