Your progress is only saved in this browser. to protect it and pick up on any device.

Connect a Postman API key to check your work

You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.

0 of 2 steps0%

Fabric Gateway: One Governed Path for Agent Execution

Fabric Gateway sits between an application or AI agent and the models, MCP servers, APIs, CLI tools, and other agents it needs to use.

Instead of making the agent connect to every destination and hold every credential itself, the agent sends requests through Fabric. Fabric applies identity, access policy, managed credentials, routing, retries, rate limits, guardrails, and observability while the application is running.

The control plane is where services are registered and policies are configured. The data plane is where Fabric enforces those decisions as traffic flows to the selected model, MCP server, API, or agent.

Fabric Gateway architecture showing the control plane configuring a data plane that governs traffic between applications and AI agents and their LLM, MCP, API, and agent providers

Important: Fabric Gateway does not replace your agent or its orchestration. It gives that orchestration one governed path to everything it needs to call.

You already have a working Banking, Fraud, and Support workflow. Start turning its scattered direct connections into one governed path by creating a model route, importing the Fraud API, and testing Fraud through Fabric from Postman.

1

Configure an LLM Route

  1. Open Fabric Gateway. Sign in, or create an account if you do not already have one.

  2. In the sidebar, select LLMs, then select the Providers tab.

  3. Locate OpenAI in the provider catalog and select Connect.

    The updated Fabric Gateway LLM provider catalog with a Connect action on each provider

  4. On Create LLM connection, confirm that Provider is set to OpenAI. Under Connection, leave these defaults unchanged:

    • Connection name: openai
    • Target URL: https://api.openai.com
    • Models: All current and future models
    • Access: Open
  5. Under Upstream auth, confirm that Auth type is Bearer token, then paste your OpenAI API key into API key. Fabric encrypts this upstream credential and stores it in its managed vault, so the support agent does not need to hold it directly.

  6. Leave Create gateway route selected. Confirm the route name is openai-route, keep the generated base path, and leave all endpoints selected.

    The Create LLM connection screen configured for OpenAI with its connection, upstream authentication, route, and endpoints

  7. Under Gateway auth, select Gateway key, then select Create key.

  8. When Gateway key created appears, select Copy key and save the key securely. It will not be shown again. Select I've saved this key, then select Done.

    The updated Gateway key created prompt with the one-time key, Copy key action, and saved-key confirmation

  9. Select Create connection. Fabric creates the OpenAI connection and its gateway route together.

  10. Open the cloned project's .env file and replace the placeholder value of FABRIC_API_KEY with the gateway key you copied:

FABRIC_API_KEY=YOUR_COPIED_GATEWAY_KEY
  1. Return to LLMs, select the Routes tab, open the ellipsis menu for openai-route, and select Copy LLM Base URL. This copies the OpenAI-compatible base URL, including /v1.

  2. Return to the cloned project's .env file and paste the copied URL as the value of FABRIC_LLM_URL:

    FABRIC_LLM_URL=YOUR_COPIED_LLM_BASE_URL

Expected outcome: Your Fabric tenant exposes the selected models through an LLM route, and the cloned support agent has the gateway credential and LLM base URL it needs to use that route.

Validation: Paste the copied LLM Base URL and Fabric Gateway Key into the verification fields below. LiftOff calls the route's /models endpoint through Fabric and confirms that it returns a model catalogue. The key is used only for this server-side request and is not saved.
2

Import and Expose the Fraud API

  1. Open your Postman workshop workspace.

  2. In the left sidebar, expand Specs, then click Intergalactic Fraud API.

  3. In the specification editor, click Code, confirm the format is YAML, then copy the complete OpenAPI definition.

  4. Switch to Fabric Gateway. In the sidebar, click Services, confirm that Connections is selected, then click Create connection.

    The updated Fabric Services page showing the Connections tab and Create connection action

  5. On Create HTTP connection, click Import OpenAPI spec under Source. Paste the YAML into OpenAPI spec, leave Import mode set to Merge, then click Preview.

    The updated Create HTTP connection screen with an OpenAPI specification, Merge import mode, and Preview action

  6. Review the Import summary. Confirm that:

    • Connection name is intergalactic-fraud-api.
    • The Target URL points to the deployed Fraud API.
    • Upstream auth is API key in the X-API-Key header.
    • Fabric found six routes, including the public /health and /openapi.yaml routes.

    The updated Fraud API import summary showing its target, X-API-Key authentication requirement, and six routes

  7. Click the action at the bottom of the summary. For a new import, it says Create connection. If the connection already exists, as shown in the screenshot, it says Update connection.

  8. On the intergalactic-fraud-api connection page, confirm that the connection is saved. Its Overview should show Access as Open and one upstream.

    The updated Intergalactic Fraud API connection overview showing open access and one upstream

  9. In Fabric's sidebar, click Credentials, then click Create credential.

    The updated Fabric Credentials page with the Create credential action

  10. Configure the credential:

  • Set Type to Upstream credential.

  • Under Connection, select intergalactic-fraud-api.

  • Confirm that Auth requirement is API key in X-API-Key header.

  • Enter Fraud API Key under Name (optional).

  • Enter the following API key:

    fraud-demo-key

The updated Create credential screen configured with an upstream X-API-Key credential for the Intergalactic Fraud API

  1. Click Create upstream credential. Fabric encrypts the key and stores it in its managed vault, then supplies it as X-API-Key when it calls the upstream Fraud API.

  2. Return to Services, open intergalactic-fraud-api, then select the Routes tab. Find the /health route, open its ellipsis menu, and select Copy DP URL.

The updated Fabric Services Routes tab showing the Copy DP URL control for the Fraud API health route

  1. The copied URL ends in /health. Remove that trailing path so that you keep only the Fraud API data-plane base URL. For example, change https://your-team.dp.fabricgateway.ai/health to https://your-team.dp.fabricgateway.ai.
  2. Open the cloned project's .env file and replace the placeholder value of FABRIC_FRAUD_API_URL with the base URL after removing /health:
FABRIC_FRAUD_API_URL=YOUR_FRAUD_DP_BASE_URL
  1. Return to your workshop workspace in Postman and open the Fraud API collection. From the environment dropdown, select Fabric Gateway.

  2. In the left sidebar, open Environments → Fabric Gateway. Paste the same base URL—without /health—into the current value of fraudBaseUrl.

    The Postman Fabric Gateway environment with the Fraud data-plane base URL populated

  3. Confirm that Fabric Gateway remains selected in the environment dropdown, open System → Check Fraud API Health, then select Send. Confirm that the public health route succeeds through Fabric Gateway without a gateway key.

  4. Open Fraud Assessments → Assess a transaction for fraud risk, then select Send.

  5. Confirm that Fabric returns a 201 Created response containing the transaction's risk score, level, and fraud signals.

    An example successful fraud assessment response in Postman showing a risk score, risk level, and fraud signals

Expected outcome: Fraud works through Fabric without exposing its upstream credential to the client.

Validation: Enter the Fraud data-plane base URL—without /health—below. LiftOff sends the same unauthenticated GET /health request through Fabric and confirms a successful response.