Consumer Integrations

This page is for NeMo Fabric, version dev. For other versions, use one of these documentation indexes: - Latest (v0.4.0) (default): https://docs.nvidia.com/nemo/fabric/latest/llms.txt - dev: https://docs.nvidia.com/nemo/fabric/dev/llms.txt - v0.5.0: https://docs.nvidia.com/nemo/fabric/v0.5.0/llms.txt - v0.4.0: https://docs.nvidia.com/nemo/fabric/v0.4.0/llms.txt - v0.3.0: https://docs.nvidia.com/nemo/fabric/v0.3.0/llms.txt - v0.2.0: https://docs.nvidia.com/nemo/fabric/v0.2.0/llms.txt - v0.1.1: https://docs.nvidia.com/nemo/fabric/v0.1.1/llms.txt - v0.1.0: https://docs.nvidia.com/nemo/fabric/v0.1.0/llms.txt

NVIDIA NeMo Fabric consumer integrations are northbound: they connect applications, services, evaluation systems, and platforms to NeMo Fabric through its public interfaces.

NVIDIA Ecosystem

NVIDIA products use the same consumer boundary to build, deploy, evaluate, and improve agents. Refer to the NVIDIA NeMo Fabric ecosystem for current and emerging integrations.

Harbor

Harbor is a consumer integration because it uses NeMo Fabric to select and run an agent harness while Harbor owns task materialization, environments, verification, rewards, and retries. Refer to the Harbor integration guide for the supported workflow.

Build a Consumer Integration

Use the public NeMo Fabric Python SDK to construct FabricConfig, manage the runtime lifecycle, and consume normalized results and artifacts. Refer to the Python SDK guide for the public integration surface.