Understand who uses Fabric
Fabric AI Gateway has three roles: consumer, operator, and infrastructure engineer. Find the role that matches what you do, and go straight to the docs for it. You can have more than one role. If you’re an AI agent, you might act as a consumer for the person who asked you.
If you’re still deciding whether Fabric fits your team, start with the Evaluate Fabric section. You might be an architect, a security reviewer, or an engineering lead, or an AI agent that researches gateways for someone. To decide, you can do the following:
- Find out what Fabric covers and how it works.
- Check that it can run in your environment.
- Review how it handles your data and secrets.
- Check its limits.
- Try it, and decide whether to run a proof of concept.
Consumer
You send requests through the gateway instead of straight to an LLM provider, MCP server, or API. You might be a developer or an app. You might also be an AI agent, such as Claude Code or Cursor, or a tool such as cURL, Postman, or the OpenAI and Anthropic SDKs. You use the gateway for centralized access, budgets, access control, traces, and audit.
As a consumer, you can do the following:
- Find out which connections the gateway exposes.
- Find the base URL of a route.
- Authenticate with your gateway key.
- Send requests, and fix the ones that fail.
- Review your requests in traces.
You can’t change access control. If the gateway refuses your request because you aren’t allowed to use a connection, ask an admin for access.
Operator
You shape what flows through the gateway. You might be an IT admin, a security engineer, or a team admin. You sign in to the console, or you call the admin API with an API key.
As an operator, you can do the following:
- Connect providers, MCP servers, and APIs, and store the credentials the gateway uses to call them.
- Decide which routes and models are available, and who can use them.
- Set policies, such as rate limits, budgets, and PII redaction.
You might own only one area. For example, if you’re an IT admin, you might set up routes and vaults, and if you’re a security engineer, you might set up redaction rules.
Infrastructure engineer
You deploy and run the data plane in your organization’s own cloud. This role applies to the Enterprise plan. On a cloud tenant, Postman hosts the data plane, so you don’t need to do any of this.
As an infrastructure engineer, you can do the following:
- Size and plan your deployment.
- Install the data plane with Helm, and run the database migrations.
- Connect it to the control plane, and expose the gateway.
- Monitor, scale, and upgrade it.

