NVIDIA NIM routing

NVIDIA NIM router for GPU-backed hosted inference

Use Sage Router as the policy layer around NVIDIA NIM / NVIDIA Cloud endpoints. Keep NVIDIA_API_KEY under your custody, expose one OpenAI-compatible endpoint to agents, and fail over across authorized GPU-backed, local, and cloud routes.

Create API key Read quickstart Browse models Integrations

NVIDIA Cloud BYOK

Configure NVIDIA NIM as an authorized provider route using your own NVIDIA_API_KEY. Sage Router sells routing, telemetry, and generated keys; it does not resell unauthorized NVIDIA access.

OpenAI-compatible setup

Point OpenAI SDKs, coding agents, and gateway-compatible clients at https://api.sagerouter.dev/v1 while the router chooses NVIDIA NIM, Ollama, OpenAI, Gemini, Anthropic, or private routes by policy.

429 failover

When an NVIDIA key, model route, or fallback provider rate-limits, Sage Router can choose another eligible authorized route instead of making every agent implement provider retry logic.

60-second NVIDIA NIM setup

export OPENAI_BASE_URL=https://api.sagerouter.dev/v1
export OPENAI_API_KEY=sk_sage_your_generated_key
export NVIDIA_API_KEY=nvapi-your_authorized_key

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "sage-router/frontier",
    "messages": [{"role": "user", "content": "Use NVIDIA NIM if it is the best healthy authorized route"}]
  }'

Credential load balancing

Credential pools can load balance and fail over across authorized NVIDIA API keys when one key is exhausted, rate-limited, or unhealthy.

Multimodal routing

Image, audio, video, and document inputs route only to capable models, and served modalities are recorded per model for better future routing.

Capability-aware policy

Auto and agentic profiles can include NVIDIA NIM without sending vision, audio, video, or document work to models that cannot handle that modality.

Why route NVIDIA NIM traffic?

NVIDIA NIM gives teams GPU-backed hosted inference and NVIDIA-backed model endpoints. Production agents still need provider policy, 429 failover, key rotation, route observability, multimodal capability gates, and local escape hatches. Sage Router keeps NVIDIA in the matrix without making it the only path.

Next steps

Create an API key, copy the hosted quickstart, browse NVIDIA-capable routes, or read the NVIDIA NIM integration guide.