Requesty
Sign in

identity

open weights
NVIDIA logo

nemotron-3.5-content-safetyNVIDIA

from /1M infreenvidia
context131K8K out
providers11 region
endpoints11 region
endpoints
1
regions
1
api
chat
released
June 2026

capabilities 2/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

endpoints

1 / 1 region
Providers serving nemotron-3.5-content-safety, with pricing and measured performance. Best value in each column is coloured.
#flags
1NVIDIAGlobal131Kfreefreefree-
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis

no published benchmark scores for this model

call it

model=
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

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
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)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

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.

questions 6

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 the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
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.

more from nvidia 6

Other NVIDIA models
modelcontextfrom /Mproviders
nemotron-lightning-3.5-30b-a3b262K$0.051
nemotron-3.5-lightning-30b-a3b1.0Mfree1
nvidia-nemotron-3-ultra262K$0.371
nemotron-3-ultra-nvfp4262K$0.601
nemotron-3-nano-omni-30b-a3b-reasoning131Kfree1
nemotron-3-ultra-550b-a55b1.0Mfree2

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. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

nemotron-3.5-content-safety1 provider1 endpointsfrom free /1M inctx 131Kupdated Sep 12