Requesty
NVIDIA logo

nemotron-3.5-content-safety

NVIDIA/Open weights/1 provider

NVIDIA Nemotron 3.5 Content Safety is a compact 4B-parameter multimodal guardrail model from NVIDIA, fine-tuned from Google Gemma-3-4B. It moderates both inputs to and responses from LLMs and VLMs, accepting text and image input and returning text output: a safe/unsafe classification for the user prompt and the response, safety category labels, and an optional reasoning trace. It covers 12 languages with a context window of up to 128K tokens. Suited for prompt and response moderation, content classification, safety pipelines, and enterprise AI guardrails with policy enforcement, and includes a togglable reasoning mode. Part of the NVIDIA Nemotron family of open models for agentic AI.More

Which id to call

nemotron-3.5-content-safety

Requesty routes this id across every provider serving nemotron-3.5-content-safety, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

From /1M input

free

NVIDIA

Context

131K

8K output

Endpoints

1

1 region

Regions

1

chat

Capabilities 2/8

VisionReasoningTool callingCachingWeb searchJSON schemaComputer useImage generation

1 endpoint / 1 region

Providers serving nemotron-3.5-content-safety

Provider prices, per 1M tokens. Pay as you go adds 5%, or 0% on your own keys.

Providers serving nemotron-3.5-content-safety, with pricing and measured performance. The best value in each column is highlighted.
RankPrivacy
1NVIDIAGlobal131Kfreefreefree-

A column is blank where no qualifying sample exists, and every row links to that provider's endpoint page.

model=

Which id to call

One base url, https://router.requesty.ai/v1, and one key for every id here.

nemotron-3.5-content-safety

Requesty routes this id across every provider serving nemotron-3.5-content-safety, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

OpenAI compatible

Call it in three lines

Change the base url, use your Requesty key, set the model to any id on the left. Existing OpenAI SDK code needs no other edit.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1", ) response = client.chat.completions.create( model="nemotron-3.5-content-safety", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ], ) print(response.choices[0].message.content)

6

More from NVIDIA

Reference

nemotron-3.5-content-safety questions

Which providers serve nemotron-3.5-content-safety?

nemotron-3.5-content-safety is available from 1 provider through Requesty: NVIDIA. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.

How much does nemotron-3.5-content-safety cost?

Pricing starts at free per million input tokens and free per million output tokens on NVIDIA, the cheapest endpoint. Prices vary by provider and region; the table above shows every endpoint. Those are the upstream provider rates: pay as you go adds 5% on top, or 0% if you bring your own provider keys.

Is nemotron-3.5-content-safety open weights?

Yes. nemotron-3.5-content-safety is an open-weights model from NVIDIA, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.

What is the context window of nemotron-3.5-content-safety?

nemotron-3.5-content-safety supports up to 131K tokens of context, with up to 8K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.

How do I use nemotron-3.5-content-safety with the OpenAI SDK?

Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "nemotron-3.5-content-safety" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.

Should I call nemotron-3.5-content-safety by its managed id or a provider id?

Use the managed id, "nemotron-3.5-content-safety". Requesty picks which of the 1 provider serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "nvidia/nemotron-3.5-content-safety" only when you need one specific deployment and want no failover.

Route nemotron-3.5-content-safety through one endpoint

One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in.

Benchmark rankings