> This page is for version 0.10.
> For other versions, use one of these documentation indexes:
> - Latest (default): https://docs.nvidia.com/nemo-helix/latest/llms.txt
> - 0.10: https://docs.nvidia.com/nemo-helix/v0.10/llms.txt
> - 0.9: https://docs.nvidia.com/nemo-helix/v0.9/llms.txt
> - 0.8: https://docs.nvidia.com/nemo-helix/v0.8/llms.txt
> - 0.7: https://docs.nvidia.com/nemo-helix/v0.7/llms.txt
> - 0.6: https://docs.nvidia.com/nemo-helix/v0.6/llms.txt
> - 0.5: https://docs.nvidia.com/nemo-helix/v0.5/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo-helix/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo-helix/_mcp/server.

# Getting Started with NeMo Safe Synthesizer

Get started with NeMo Safe Synthesizer for generating private synthetic versions of sensitive tabular datasets through the platform Jobs service.

## Prerequisites

Before using NeMo Safe Synthesizer, complete [Setup](/nemo-helix/v0.10/documentation/get-started) to install the CLI/SDK.

Using NeMo Safe Synthesizer has the following additional requirements:

* A GPU-capable Jobs backend with 80GB+ VRAM available for Safe Synthesizer tasks.
* Sufficient disk space for generated datasets (50GB+ recommended)

For general platform troubleshooting (port conflicts, health checks, and so on), refer to [Setup](/nemo-helix/v0.10/documentation/get-started).

> **Note**
>
> When you configure NVIDIA Build with `nemo setup`, it registers the `nvidia-build` model provider
> in the setup workspace (`--workspace`, otherwise the active context workspace, falling back to `default`).
> These tutorials assume setup used `default`, so they reference `default/nvidia-build`.
> If you used another workspace, substitute `<workspace>/nvidia-build` and list providers in that workspace.
> This provider routes inference requests to models hosted on `build.nvidia.com` using the API base URL `https://integrate.api.nvidia.com`
> and the NGC API key with `Public API Endpoints` permissions provided during deployment.
>
> You can verify this provider exists by running `nemo inference providers list --workspace default`.
>
> The tutorials in these docs use this provider for inference, but you can alternatively create your own and use it instead.
>
> The NVIDIA provider-creation and evaluation examples support `NVIDIA_BASE_URL`, an OpenAI-compatible API base including `/v1`. The default is `https://integrate.api.nvidia.com/v1`. For another service, export its base URL (for example, `export NVIDIA_BASE_URL=https://inference-api.nvidia.com/v1`) and set `NVIDIA_API_KEY` to a credential authorized for that service. Model identifiers and access must also match the service. Set `NVIDIA_MODEL` to the exact chat-model ID from that service's `/v1/models` catalog; no override retains each example's public NVIDIA Build default. Anonymizer examples also support `NHX_ANON_GENERAL_MODEL` for their general-purpose model. Retrieval examples give the more specific `RETRIEVAL_CHAT_MODEL` priority over `NVIDIA_MODEL` and support `RETRIEVAL_EMBED_MODEL` for the embedding model. This does not automatically change providers you have already registered.

---

## CLI, Jobs API, and SDK

Safe Synthesizer jobs run through the platform Jobs service. Upload input data to the Files service, then create a job with the CLI, Jobs API, or the Python SDK builder.

Example:

```shell
nemo files filesets create my-input --exist-ok
nemo files upload ./data.csv my-input
cat <<EOF > ./nss-job.json
{
  "data_source": "default/my-input#data.csv",
  "config": {
    "replace_pii": {
      "globals": {
        "classify": {
          "classify_model_provider": "default/nvidia-build"
        }
      }
    }
  }
}
EOF
nemo safe-synthesizer generate \
  --workspace default \
  --spec-file ./nss-job.json
```

Note the job name in the command output, then use it to watch the job and download its results:

```shell
nemo jobs watch <job-name>
nemo jobs results download synthetic-data --job <job-name> --output-file ./synthetic-data.csv
nemo jobs results download evaluation-report --job <job-name> --output-file ./evaluation_report.html
```

To create the same job from Python, use `SafeSynthesizerJobBuilder`, which uploads local data for you; see [SDK Resources](/nemo-helix/v0.10/documentation/synthesize-safe-data/sdk-resources).
To call the Jobs API directly, send the same spec as the request body; see the [Safe Synthesizer API Reference](/nemo-helix/v0.10/documentation/reference/api-reference).

---

## Next Steps

Create your first synthetic dataset:

* [Safe Synthesizer 101 Tutorial](/nemo-helix/v0.10/documentation/synthesize-safe-data/tutorials/safe-synthesizer-101) - a beginner-friendly introduction
* [SDK Resources](/nemo-helix/v0.10/documentation/synthesize-safe-data/sdk-resources) - Python SDK methods for jobs, builders, logs, and results

---