Quickstart for NIM Metadata API
This Quickstart walks you through identifying a NIM microservice, making your first request, and reading the response. For the requirements you need first, refer to Prerequisites.
Prerequisites
Before you start, complete the following prerequisites:
- Install an HTTP client, such as curl or the Python
requestslibrary. - Collect the
resourceIdand tag for the NIM microservice you want to inspect, as described in Prerequisites.
Quickstart Steps
To quickly get started with the NIM Metadata API, complete the following steps.
-
Identify the NIM microservice by its
resourceIdand tag.The
resourceIdis a slash-separated repository path, and the tag is the container tag as it appears in the catalog. For this example, usenim/nvidia/parakeet-1-1b-rnnt-multilingualand1.5.0. -
Make the request against the query-parameter form of the endpoint.
curl
Python
A 200 status code returns the metadata document. A 404 status code means this combination of NIM microservice and tag has no published metadata.
-
Read the four top-level sections of the response.
All four are optional.
profiles: The deployable configurations. This is the section you use most.release_details: Release-level facts, such as version, documentation, compliance, and supported architectures.features: Capability flags, such as context window, tool calling, and backend support.related_urls: Links to related resources.
-
Compare the profiles against your hardware.
The following abridged response shows a NIM microservice with GPU-specific profiles:
This response describes two profiles, two different GPUs, and two different vRAM floors. If you have L40S GPUs with 48 GB each, the second profile fits and the first does not. That comparison, made in one request before you download anything, is the core purpose of this API.
-
Recognize the GPU-agnostic case.
Many NIM microservices ship profiles that run anywhere with sufficient vRAM. Those profiles omit
gpuandgpu_deviceentirely, and can carry an emptytested_gpu_devicesarray:This is not an empty or broken response. Read it as “no GPUs tested with the profile” rather than “no GPUs supported.” For the full set of GPU targeting signals, refer to Core Concepts Overview.
Minimal Code Example
Use the following self-contained example to fetch a metadata document and report the profiles that fit a given vRAM budget:
Next Steps
Now that you have a working request, explore the following resources in greater detail:
- Select a profile for real hardware: Choose a Profile for Your Hardware
- Learn the fundamentals: Core Concepts Overview
- Look up every field: Response Fields
- Build a durable integration: Notes for Automated Agents