{"version":1,"type":"story","url":"https://digestai.news/story/moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal","json":"https://digestai.news/story/moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal.json","markdown":"https://digestai.news/story/moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal.md","slug":"moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal","headline":"MoEngage uses Amazon Bedrock AgentCore Gateway to expose 400 internal APIs as agent tools","summary":"MoEngage, a customer‑engagement platform used by more than 1,350 consumer brands, operates roughly 400 internal REST APIs built by 25 engineering teams across seven AWS regions. The company needed AI agents to call these APIs safely, without public exposure, without giving models direct control over identity, and without flooding context windows with hundreds of tool definitions.\n\nTo solve this, MoEngage adopted Amazon Bedrock AgentCore Gateway, a fully managed Model Context Protocol (MCP) server. By registering OpenAPI specs, the gateway automatically generates MCP tools, applies Cedar policies for per‑agent authorization, and routes calls through managed egress over Amazon VPC Lattice. This eliminated the need for more than 20 separate MCP servers, saved an estimated six months of platform‑engineering effort, and cut the onboarding time for a new API from days to hours.\n\nThe deployment now runs in seven regions, serving about 400 registered API operations to ten internal agents. It uses SigV4 signing for identity, keeps all traffic private via VPC interface endpoints, and offers semantic search so agents receive only the tools they need, keeping context windows small and execution efficient.","keyPoints":["MoEngage turned ~400 private APIs into agent tools via Amazon Bedrock AgentCore Gateway.","The managed solution eliminated 20+ MCP servers, cutting platform engineering effort by an estimated six months.","Onboarding a new API now takes hours, not days, with no public endpoints and server‑side policy scoping."],"whyItMatters":"It shows how large enterprises can securely scale AI agents across hundreds of internal services without exposing them, reducing engineering overhead and enabling faster AI‑driven automation.","category":{"slug":"agents","name":"Agents & Tools","url":"https://digestai.news/category/agents"},"entities":{"companies":["MoEngage","Amazon","AWS"],"models":[],"people":["Nikhil Kumar","Shakir Khan"]},"firstPublishedAt":"2026-10-29T16:54:52Z","updatedAt":"2026-10-29T16:54:52Z","sourceCount":1,"hasPrimarySource":true,"sources":[{"outlet":"AWS Machine Learning Blog","title":"How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway","url":"https://aws.amazon.com/blogs/machine-learning/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway","publishedAt":"2026-10-29T16:54:52Z","type":"primary","primary":true,"lead":true}],"sourceNotes":null,"discussions":[],"thread":{"title":"Amazon Bedrock Enterprise AI Agent Ecosystem Expansion","url":"https://digestai.news/thread/octave-reliance-builds-secure-multi-tenant-ai-foundation-on-amazon-bedrock","storyCount":4},"cite":{"text":"Digest AI, \"MoEngage uses Amazon Bedrock AgentCore Gateway to expose 400 internal APIs as agent tools\", 29 October 2026, https://digestai.news/story/moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal","publisher":"Digest AI","title":"MoEngage uses Amazon Bedrock AgentCore Gateway to expose 400 internal APIs as agent tools","datePublished":"2026-10-29T16:54:52Z","url":"https://digestai.news/story/moengage-uses-amazon-bedrock-agentcore-gateway-to-expose-400-internal"},"generatedBy":"Written by Digest AI's editorial model from the linked sources; the sources are the record.","license":"Headlines, digests and key points are written by Digest AI and may be quoted with a link to the story page. Linked articles belong to their publishers. Terms: https://digestai.news/terms#reuse"}