
Argent with NVIDIA NIM
Run models on your own hardware and govern them like any cloud model. Argent applies the same approved list, redaction, budgets and signed record to NVIDIA NIM, with no key to manage and no data leaving your network.
What Argent does with NVIDIA NIM
NVIDIA NIM packages models as services you run on your own infrastructure. Argent governs it like any cloud provider, and nothing has to leave your network.
- Built in: NVIDIA NIM's connection settings ship with Argent.
- No key needed: the endpoint is marked self-hosted and keyless, so Argent fetches nothing from a vault for it.
- Metered on streams: some self-hosted engines report token use on a stream only when asked. Argent asks for them, so cost metering works.
- Approved models and rules: the same approved list and access rules as every provider.
- Local data protection: the sensitive-data detector runs as part of Argent, so prompts are scanned without sending text anywhere else.
How it connects
Register the engine, price its models, point agents at Argent.
- Register the engine on the AI Providers page as a self-hosted, keyless endpoint.
- Register each agent with an owner. It gets its own Argent key and copy-paste setup.
- Point it at Argent. The agent's base URL becomes its gateway route.
- Price your models. Add your internal rate per model in the price book, in USD per million tokens, so budgets count self-hosted use. An agent under a budget that calls a model with no price is refused.
Argent itself can run inside your network with no internet connection. See Air-Gapped Install and Air-gapped on-prem.
What you configure
Everything below is set once in the Argent console and applies to every agent that calls NVIDIA NIM through the gateway.
| Setting | Where | What it does |
|---|---|---|
| Approved models | Policy > Model and endpoint access | Default deny: a call is allowed only when the model is on the approved list. The list is platform AND tenant AND agent, and each layer can only narrow the one above. |
| Access rules | Same page | Allow or deny by provider, route type, model, hosted tools, function tools and output type, for the tenant, a department, a person or one agent. The narrowest rule wins, and a 7-day impact preview shows what a draft would change. |
| Sensitive data | DLP | Per entity type: redact and record, record only, or block the request. |
| Budgets and caps | Budgets | Budgets for the company, org, department, person and agent. Each request is priced and held against the budget before it leaves, and an emergency cap stops a runaway agent now. |
| Mode | Per control | Off, watch or enforce. Watch records what would have been refused and changes nothing on the wire. |
Start in watch, read what would have been refused, then switch on enforce. See Watch Before You Enforce.
One request, step by step
What happens between your agent and NVIDIA NIM, in order.
- The agent sends its request to its Argent route, carrying its own Argent key and nothing from NVIDIA NIM.
- Who is calling. Argent identifies the agent from its key and checks it may use this endpoint. The endpoint comes from the route the gateway matched, never from a header the caller sets.
- Which model. Argent reads the model from the request and checks it against the approved list and access rules before anything leaves.
- Refuse or allow. A model nobody approved is refused at the gateway with a named reason, such as
llm.deny.model. - Sensitive data. The request is scanned by a reader that knows the NVIDIA NIM format, and secrets and personal data are redacted, recorded or blocked under your policy. If the scan cannot run, the request is refused, never passed as clean.
- Budget. The request is priced and the amount is held against the agent's budget, so parallel calls cannot overshoot it.
- No key. The endpoint is keyless, so nothing is fetched or attached.
- Reply and record. Token usage is read from the reply, the cost is settled, and the signed record is written.
What the record shows
Every NVIDIA NIM call leaves one signed record, allowed or refused.
- One row per call: the agent and the person who owns it, the tenant, the model, the decision and the policy that made it, latency, and the cost, token and cache figures.
- Tamper-evident: each row is hash-chained to the one before and signed with an ed25519 key held in Vault Transit, so an edited or missing row shows.
- Real cost: cost comes from the usage block in NVIDIA NIM's own reply, priced from your price book in USD per million tokens.
- No unpriced spend: an agent under a budget that calls a model with no price is refused, so a new model cannot slip past a cap.
Conversations can be opened and replayed from the record. See Session Replay and One-Click Audit Evidence.
Related capabilities and goals
Where to go next.
- Capabilities: Air-Gapped Install, Model Control, Sensitive Data Redaction, AI Spend Caps.
- Goals: Sovereign AI, Model control and routing, Budget and token spend.
- Works with: vLLM, Hugging Face TGI, Kubernetes and Helm, Air-gapped bundle, AI in regulated and air-gapped environments.
- Everything else Argent connects to: All integrations.
Download files
- PDFArgent Model Control data sheetApproved models, Model Swap, model classes and failover. One page.
- PDFArgent Air-Gapped Install data sheetRun Argent inside your own network with no internet connection. One page.
- PDFArgent Sensitive Data Redaction data sheetPersonal data and secrets found and redacted before a prompt leaves. One page.
Want this running on your own use cases?
All downloads