How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway
MoEngage turned roughly 400 private REST APIs across 7 AWS Regions into permission-scoped agent tools with Amazon Bedrock AgentCore Gateway. No per-service MCP servers, no public endpoints, and no 400-tool context bloat. See how OpenAPI specs, Cedar policies, and managed Amazon VPC Lattice egress made it work.
MoEngage, a leading agentic customer engagement platform used by over 1,350 consumer brands, faced the challenge of making hundreds of private APIs accessible to AI agents securely and efficiently. The platform relied on roughly 400 internal REST APIs running in private VPCs across seven AWS Regions, with no public exposure. To address this issue, MoEngage implemented AgentCore Gateway, a feature of Amazon Bedrock AgentCore, to convert these private APIs into permission-scoped agent tools.
This solution saved an estimated six months of engineering effort and streamlined the onboarding process for new APIs, making it much easier and faster.
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
