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 1 steps0%

Review the governed support-agent architecture you assembled, the differences you observed between Direct and Fabric, and the practices to carry into a production implementation.

1

Review What You Built

You started with a working fintech support agent that held separate connections to its model, Banking MCP server, Support MCP server, and Fraud API. Without changing the agent's orchestration logic, you placed Fabric Gateway between the agent and those upstream services.

Your completed Fabric path

CapabilityWhat you configuredResult
Model accessAn LLM service and route with its provider credential stored in Fabric's managed vaultThe agent calls the model through a governed Fabric URL without holding the provider key
Fraud assessmentThe Fraud API imported from its OpenAPI definition, plus a managed service credentialFabric supplies the upstream API key and exposes the API through the data plane
Banking and Support toolsTwo authenticated MCP services exposed through one routeThe agent manages one MCP connection instead of two
Tool discoveryTool Search on the combined MCP routeFabric replaces 103 complete MCP definitions with search_tool, get_tool, and execute_tool
Model governanceAn LLM Rate Limit instance on the model routeFabric enforces a token budget and returns a 429 when the lane exceeds it
Adaptive model routingAn Adaptive Model Router instance backed by a decision serviceFabric can match model capability and reasoning effort to each prompt's difficulty
Operational evidenceAnalytics and TracesYou can examine aggregate usage and investigate individual requests and policy decisions

What the comparison demonstrated

  • Direct begins with 104 tools and sends their definitions to the model without passing through your Fabric policies.
  • Fabric Gateway begins with four tools—the three Tool Search discovery tools and the Fraud function—while retaining access to the underlying Banking and Support capabilities.
  • The smaller Fabric catalogue uses fewer tool-schema tokens, less context, fewer model tokens, and typically costs less to run. Exact measurements vary between runs.
  • A policy added at the gateway changed the Fabric lane's behavior without requiring a change to the support agent or model provider.
  • The Direct lane remained unaffected, making the side-by-side run clear evidence that Fabric enforced the 429 response.

Key takeaways

  1. Fabric Gateway does not replace the agent or its orchestration. It gives that orchestration one governed path to the services it needs.
  2. Managed credentials keep upstream secrets out of agent code and client requests.
  3. A single route can aggregate multiple MCP services, while prefixes preserve each tool's source and prevent naming collisions.
  4. Tool Search progressively discloses capabilities instead of loading an entire tool catalogue into every model turn.
  5. Adaptive model routing can reserve more capable models for harder work while sending straightforward requests to less expensive configurations.
  6. Plugins apply policy centrally, and Analytics and Traces provide evidence of what happened at runtime.

Clean up your workshop configuration

  • Disable or remove the temporary workshop-llm-token-limit instance if you have not already done so.
  • Treat the public MCP routes used in this workshop as a learning configuration. Use gateway authentication and access policies appropriate to your users and environment before deploying a production workload.
  • Keep provider, API, MCP, and gateway credentials out of source control. Rotate any credential that may have been exposed.

Expected outcome: You can explain the end-to-end architecture, identify where Fabric applies credentials and policy, and describe why the governed Fabric lane uses fewer model resources than Direct.

Validation: [MANUAL] Learner reviewed the completed architecture, key outcomes, and cleanup guidance.