---
format: "aidr-story-markdown/v1"
id: "fa73a25059b17ce1669d18b7a19f97117b8a8d08e462b863a8388da619b041d8"
canonical_url: "https://aidr.today/fa73a250?lang=en"
title: "How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway"
lang: "en"
requested_lang: "en"
available_langs: ["en","vi"]
translation_fallback: null
fallback_fields: []
published_at: "2026-10-29T16:54:52.000Z"
category: "Tools"
topics: ["amazon","agent","devtools"]
source_urls: ["https://aws.amazon.com/blogs/machine-learning/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway/"]
summary: "MoEngage turned roughly 400 private REST APIs across 7 AWS Regions into permission-scoped agent tools with Amazon Bedrock AgentCore Gateway, using OpenAPI specs, Cedar policies, and managed Amazon VPC Lattice egress without per-service MCP servers, public endpoints, or 400-tool context bloat."
---

# How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway

> [Open the canonical story](<https://aidr.today/fa73a250?lang=en>)

**Published:** 2026-10-29T16:54:52.000Z
**Category:** Tools
**Topics:** amazon, agent, devtools

## Summary

MoEngage turned roughly 400 private REST APIs across 7 AWS Regions into permission\-scoped agent tools with Amazon Bedrock AgentCore Gateway, using OpenAPI specs, Cedar policies, and managed Amazon VPC Lattice egress without per\-service MCP servers, public endpoints, or 400\-tool context bloat\.

## Sources

- [Story source](<https://aws.amazon.com/blogs/machine-learning/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway/>)

