The enterprise customer platform unified distributed internal services across seven cloud regions without compromising strict data residency boundaries or exposing resources to the public web. Product teams simply deliver REST APIs alongside OpenAPI specifications, leaving the centralized AI Platform team to handle the underlying connection layers. To maintain security, sensitive details like user roles and database identities are directly injected by calling services rather than exposed as tool parameters that agents could alter. This streamlined approach allowed the company to bypass the deployment of more than 20 distinct Model Context Protocol servers.
Key points
Onboarding turnaround times for integrating new internal APIs fell from multiple days to…: Onboarding turnaround times for integrating new internal APIs fell from multiple days to just hours.
Sensitive contextual data such as tenant, user, and role identities are injected by the c…: Sensitive contextual data such as tenant, user, and role identities are injected by the caller instead of model parameters.
Private internal APIs remain isolated within private virtual clouds without needing rever…: Private internal APIs remain isolated within private virtual clouds without needing reverse proxies or public endpoints.
Sources checked by our analysis pipeline: 1
Artificial Intelligence
How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway
This post was co-written with Nikhil Kumar and Shakir Khan from MoEngage.
When engineering teams start building AI agents, the capabilities those agents need usually already exist as internal APIs. Campaign creation, segment queries, delivery stats. The challenge isn’t building new functionality. The challenge is making hundreds of private APIs safely reachable by agents without exposing them to the public internet, without giving models control over identity, and without flooding context windows with hundreds of tool definitions.
MoEngage, the agentic customer engagement platform that more than 1,350 consumer brands use to deliver personalized experiences across push, email, in-app, SMS, WhatsApp, and RCS, faced exactly this problem. Behind the product sit roughly 400 internal REST APIs, built by 25 engineering teams, running in private virtual private clouds (VPCs) across seven AWS Regions. MoEngage isolates these APIs regionally to meet data residency commitments and doesn’t expose them to the public internet. The capability the agents needed was already running in production. Making it reachable, safely, was the hard…
The social media giant is testing new consumer software that digitizes personal wardrobes to automate daily styling and trip planning. Available across select Southeast Asian markets, the tool reflects an ongoing corporate strategy to rapidly release experimental products built using automated development efficiencies.
Defense network oversight faces fresh scrutiny after an unauthorized artificial intelligence tool bypassed standard safeguards for an extended period. The security lapse involved a contractor operating the program directly within internal Pentagon systems. Officials moved to patch the vulnerability immediately after uncovering the software's active data transmissions.
The organization revised its core framework to establish human intent as the primary guiding principle for artificial intelligence behavior. By formally updating these operational parameters, the company aims to ensure future system deployments align directly with what people actually want and mean. This strategy directs developers and models to focus on authentic human needs across all generated outputs.