For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Welcome
    • Contributing
  • Concepts
    • Columns
    • Seed Datasets
    • Agent Rollout Ingestion
      • Default Model Settings
      • Configure with the CLI
      • Custom Model Settings
      • Model Providers
      • Model Configs
      • Inference Parameters
    • Custom Columns
    • Validators
    • Processors
    • Person Sampling
    • Traces
    • Architecture & Performance
    • Deployment Options
    • Security
  • Tutorials
    • Overview
    • The Basics
    • Structured Outputs, Jinja Expressions, and Conditional Generation
    • Seeding with an External Dataset
    • Providing Images as Context
    • Generating Images
    • Image-to-Image Editing
  • Recipes
    • Recipe Cards
  • Plugins
    • Overview
    • Example Plugin
    • FileSystemSeedReader Plugins
    • Discover
  • Code Reference
    • Overview
  • Dev Notes
    • Overview
    • Prompt Sensitivity
    • Retriever SDG Toolkit
    • Have It Your Way
    • VLM Long Document Understanding
    • Push Datasets to Hugging Face Hub
    • Text-to-SQL for Nemotron Super
    • Async All the Way Down
    • Owning the Model Stack
NVIDIANVIDIA
Developer-friendly docs for your API
Privacy Policy | Manage My Privacy | Do Not Sell or Share My Data | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026, NVIDIA Corporation.

LogoLogoNeMo Data Designer
On this page
  • Model Providers
  • NVIDIA Provider (nvidia)
  • OpenAI Provider (openai)
  • OpenRouter Provider (openrouter)
  • Model Configurations
  • NVIDIA Models
  • OpenAI Models
  • OpenRouter Models
  • Using Default Settings
  • How Default Model Providers and Configurations Work
  • Important Notes
  • See Also
ConceptsModels

Default Model Settings

||View as Markdown|
Previous

Agent Rollout Ingestion

Next

Configuring Model Settings Using The CLI

Data Designer ships with pre-configured model providers and model configurations that make it easy to start generating synthetic data without manual setup.

Model Providers

Data Designer includes a few default model providers that are configured automatically:

NVIDIA Provider (nvidia)

  • Endpoint: https://integrate.api.nvidia.com/v1
  • API Key: Set via NVIDIA_API_KEY environment variable
  • Models: Access to NVIDIA’s hosted models from build.nvidia.com
  • Getting Started: Sign up and get your API key at build.nvidia.com

The NVIDIA provider gives you access to state-of-the-art models including Nemotron and other NVIDIA-optimized models.

OpenAI Provider (openai)

  • Endpoint: https://api.openai.com/v1
  • API Key: Set via OPENAI_API_KEY environment variable
  • Models: Access to OpenAI’s model catalog
  • Getting Started: Get your API key from platform.openai.com/api-keys

The OpenAI provider gives you access to GPT models and other OpenAI offerings.

OpenRouter Provider (openrouter)

  • Endpoint: https://openrouter.ai/api/v1
  • API Key: Set via OPENROUTER_API_KEY environment variable
  • Models: Access to a wide variety of models through OpenRouter’s unified API
  • Getting Started: Get your API key from openrouter.ai

The OpenRouter provider gives you access to a unified interface for many different language models from various providers.

Model Configurations

Data Designer provides pre-configured model aliases for common use cases. When you create a DataDesignerConfigBuilder without specifying model_configs, these default configurations are automatically available.

NVIDIA Models

The following model configurations are automatically available when NVIDIA_API_KEY is set:

AliasModelUse CaseInference Parameters
nvidia-textnvidia/nemotron-3-nano-30b-a3bGeneral text generationtemperature=1.0, top_p=1.0
nvidia-reasoningnvidia/nemotron-3-super-120b-a12bReasoning and analysis taskstemperature=1.0, top_p=0.95, extra_body={"reasoning_effort": "medium"}
nvidia-visionnvidia/nemotron-nano-12b-v2-vlVision and image understandingtemperature=0.85, top_p=0.95
nvidia-embeddingnvidia/llama-3.2-nv-embedqa-1b-v2Text embeddingsencoding_format="float", extra_body={"input_type": "query"}

OpenAI Models

The following model configurations are automatically available when OPENAI_API_KEY is set:

AliasModelUse CaseInference Parameters
openai-textgpt-4.1General text generationtemperature=0.85, top_p=0.95
openai-reasoninggpt-5Reasoning and analysis taskstemperature=0.35, top_p=0.95
openai-visiongpt-5Vision and image understandingtemperature=0.85, top_p=0.95
openai-embeddingtext-embedding-3-largeText embeddingsencoding_format="float"

OpenRouter Models

The following model configurations are automatically available when OPENROUTER_API_KEY is set:

AliasModelUse CaseInference Parameters
openrouter-textnvidia/nemotron-3-nano-30b-a3bGeneral text generationtemperature=1.0, top_p=1.0
openrouter-reasoningopenai/gpt-oss-20bReasoning and analysis taskstemperature=0.35, top_p=0.95
openrouter-visionnvidia/nemotron-3-nano-omni-30b-a3b-reasoning:freeVision and image understandingtemperature=0.60, top_p=0.95
openrouter-embeddingopenai/text-embedding-3-largeText embeddingsencoding_format="float"

Using Default Settings

Default settings work out of the box - no configuration needed! Simply create DataDesigner and DataDesignerConfigBuilder instances without any arguments, and reference the default model aliases in your column configurations.

For a complete example showing how to use default model settings, see the Getting Started page.

How Default Model Providers and Configurations Work

When the Data Designer library or the CLI is initialized, default model configurations and providers are stored in the Data Designer home directory for easy access and customization if they do not already exist. These configuration files serve as the single source of truth for model settings. By default they are saved to the following paths:

  • Model Configs: ~/.data-designer/model_configs.yaml
  • Model Providers: ~/.data-designer/model_providers.yaml

While these files provide a convenient way to specify settings for your model providers and configuration you use most often, they can always be set programmatically in your SDG workflow.

You can customize the home directory location by setting the DATA_DESIGNER_HOME environment variable:

$# In your .bashrc, .zshrc, or similar
$export DATA_DESIGNER_HOME="/path/to/your/custom/directory"

These configuration files can be modified in two ways:

  1. Using the CLI: Run CLI commands to add, update, or delete model configurations and providers
  2. Manual editing: Directly edit the YAML files with your preferred text editor

Both methods operate on the same files, ensuring consistency across your entire Data Designer setup.

Important Notes

API Key Requirements

While default model configurations are always available, you need to set the appropriate API key environment variable (NVIDIA_API_KEY, OPENAI_API_KEY, or OPENROUTER_API_KEY) to actually use the corresponding models for data generation. Without a valid API key, any attempt to generate data using that provider’s models will fail.

Hosted Provider Data Handling

The default model providers call hosted endpoints operated by NVIDIA, OpenAI, OpenRouter, or their upstream providers. Provider terms and privacy practices apply independently of Data Designer, and free or trial endpoints may log request data for security, operations, or product improvement. Do not submit confidential information or personal data, including faces, voices, screenshots, regulated data, or other sensitive content, unless the selected provider and endpoint are approved for your use case.

Deprecated: implicit default provider routing

The default: key in ~/.data-designer/model_providers.yaml and the registry-level “default provider” concept are deprecated and will be removed in a future release. Specify provider= explicitly on every ModelConfig instead — the built-in defaults above already do this, and a DeprecationWarning is now emitted whenever the legacy routing is exercised. See issue #589.

Environment Variables

Store your API keys in environment variables rather than hardcoding them in your scripts:

$# In your .bashrc, .zshrc, or similar
$export NVIDIA_API_KEY="your-api-key-here"
$export OPENAI_API_KEY="your-openai-api-key-here"
$export OPENROUTER_API_KEY="your-openrouter-api-key-here"

See Also

  • Custom Model Settings: Learn how to create custom providers and model configurations
  • Configure Model Settings With the CLI: Learn how to use the CLI to manage model settings
  • Model Configurations: Learn about model configurations