Launch Video Library · Devtools · Launch · 2026

Postman Fabric Gateway

Postman introduces Fabric Gateway, a centralized routing system for managing AI agent traffic, credentials, and observability across models and MCP servers.

What Postman shipped

Postman expands its API ecosystem with Fabric Gateway, a centralized routing layer designed specifically for AI agent traffic. The system sits between agents and their dependencies—models, REST APIs, and MCP servers—to handle credentials, policies, and observability.

By demonstrating a complex fintech support workflow, Postman highlights the friction of direct agent connections versus the streamlined architecture of their new gateway. The focus is on progressive tool discovery, replacing hundreds of exposed tool definitions with a simplified search interface.

How the motion works

When demonstrating a before-and-after architecture like direct connections versus a centralized gateway, a match-cut can be highly effective. Designers might try transitioning seamlessly from a tangled web of direct agent dependencies to the clean, hub-and-spoke model of the Fabric Gateway, keeping the central agent node anchored on screen to ground the viewer's spatial awareness.

For a demo heavily reliant on code and API logs, a punch-in technique helps direct focus. Rather than showing a static full-screen interface, the camera can push in sharply on the specific credential fields or policy routing rules being discussed, cutting out extraneous UI noise and ensuring the viewer absorbs the exact architectural shift.

To illustrate the reduction from 104 exposed tool definitions down to just three search endpoints, a stagger animation could map the old definitions collapsing into the new, streamlined gateway interface. Combining this with a hard-cut between the complex and simple states emphasizes the immediate structural relief the product provides.

What to steal from it

  • Anchor complex architectural comparisons around a single, fixed visual element to maintain viewer orientation.
  • Use sharp scale changes to direct attention when presenting dense technical interfaces or code blocks.
  • Contrast chaotic legacy systems with clean new architectures using abrupt, un-eased cuts to emphasize structural relief.
  • Frame technical demonstrations around a concrete, relatable use case, like a disputed bank transfer, to ground abstract concepts.

Want a video like this for your product?

Impractical cuts one from a single prompt — the same motion craft, in about twenty minutes.