Fragmented AI access
Teams integrate models, MCP servers and internal APIs independently, creating inconsistent access and duplicated infrastructure.
With Fabric: Connect every AI service through one governed gateway.
LLMs, MCP servers, APIs, and agents, routed, governed, and observed through a single endpoint deployed inside your own cloud.
50+ providers1,200+ modelsLLM, MCP, A2A and API supportPostman-hosted or hybrid deployment
Fabric Gateway is an AI-native gateway built for agents, LLMs, MCP servers, and the systems they interact with.
Why Fabric Gateway
What breaks when AI adoption expands across teams—and how Fabric restores control.
Teams integrate models, MCP servers and internal APIs independently, creating inconsistent access and duplicated infrastructure.
With Fabric: Connect every AI service through one governed gateway.
Outages, latency spikes and rate limits can disrupt every application relying on a provider.
With Fabric: Use health-aware routing, retries, circuit breakers and automatic fallbacks.
Application-level guardrails and permissions drift as more teams and workloads are added.
With Fabric: Define policy centrally and enforce it across models, agents, tools and APIs.
Organizations struggle to understand which teams, applications and models are driving token usage and cost.
With Fabric: Attribute usage, set budgets and enforce token-aware limits in real time.
Security teams cannot reliably determine who initiated an action, which policies applied or what an agent accessed.
With Fabric: Capture identity, routing, policy and authorization outcomes for every governed request.
Fabric separates centralized configuration and governance from runtime traffic. The control plane manages policy and identity, while the data plane routes requests inside the selected deployment environment.
Your stack
Applications
HTTP or any LLM SDK
AI agents
MCP · A2A
CLI tools
Claude Code · Codex · Cursor
Developers
Any HTTP client
Control plane
Postman Cloud
Registry
APIs · MCP · Agents
LLMs · CLIs
Policy & config manager
Versioning & syncing
Identity & RBAC
Organization → namespace
→ consumer
Admin portal
Analytics · Audit
UI & management
Data plane
Postman cloud (Free) or your cloud (Enterprise)
Protocol adapters
LLM · MCP · A2A
Plugin chain
Auth · Rate limit
PII · Transforms + more
Credential broker
OAuth · AES-256
Vault · Key management
Router
Radix tree
Weighted LB · Failover
OTel
Traces · Metrics · Logs
or export to your stack
Providers
LLM providers
1,200+ models across
70+ providers
MCP servers
REST APIs
Any HTTP backend
External & internal agents
Platform checklist
Auto-failover
Circuit breaker & retry
Rate limits
Request and token limits
Observability
Cost, latency, audit logs
Secret isolation
On managed routes, agents never see keys
Guardrails
PII redaction, access control, audit trail
Capabilities
Built for developers and designed for the enterprise.
Route models, MCP servers, agents and internal APIs through one endpoint, with consistent authentication, governance and observability across every connection. Import a REST API from its OpenAPI spec and Fabric validates requests against it.
Apply authentication, authorization, budgets and data controls centrally across teams, agents, models, tools and environments.
Agents use scoped Fabric tokens while the data plane retrieves and injects the correct upstream credential at request time.
Fabric understands models, tokens, streaming responses and tool calls, enabling token-aware limits, resilient routing and configurable provider fallbacks, including on any non-2xx response, with analytics on every fallback.
Follow model, MCP, agent and API calls across one workflow, with identity, policy, latency, token and cost context.
Validate the initiating user and executing agent, restrict delegated permissions and deny requests when identity or policy cannot be verified.
AI spend
Two sides of the same bill: make every request cheaper, and see and cap what every team, user and agent spends.
Pay less for every request, without changing your code.
Know who is spending what, and stop it before the bill does.
Coverage
LLMs, MCP servers and your own services, registered once and governed the same way.
1,200+ models from 50+ providers through one OpenAI-compatible endpoint. Change the base URL; keep your SDK.
base_url = https://api.fabricgateway.ai/v1
// Point your SDK here, no other code changes.
1,200+ models across 50+ providers
Point a supported SDK at Fabric by changing the base URL.
Retries, fallbacks and circuit breakers across providers.
Apps never hold upstream provider keys.
Ecosystem
Point your coding agent at Fabric and its model and MCP traffic gets the same routing, limits and traces as the rest of your stack.
LLMs
MCPs
APIs
Zero Trust
When work moves between agents and tools, Fabric carries only the identity and permissions each hop needs, and denies the request when it cannot verify either.
Check the initiating user and the executing agent on every request before anything runs.
Issue purpose-scoped access per hop instead of forwarding the original user token.
Allow only the tools and actions the agent is permitted to use.
If identity or policy cannot be verified, Fabric denies the request.
For the Enterprise
Choose the deployment model that fits your security review.
Let Postman operate it for you with regional data planes.
Control plane managed by Postman; data plane stays in your cloud.
Give each team its own connections, services, analytics and traces, with Super admin and Member roles set per namespace.
Sign in to the Fabric console through the identity provider you already use.
Use your own keys for each model provider; Fabric stores and injects them so apps never hold them.
Connect your first model, MCP server or internal API and apply consistent governance from one gateway.