> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/nemo-platform/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo-platform/_mcp/server. # About Agents An agent on NeMo Platform calls tools, accesses models through shared Platform infrastructure, and runs as a service you can register, deploy, and invoke. New agents use the Platform-managed `nemo-agents-spec-v1` `agent.yaml` contract. Legacy NVIDIA NeMo Agent Toolkit (NAT) workflow configurations remain supported, including NAT-specific evaluation and optimization commands. Both formats are managed through the `nemo agents` command group. ## How It Works A platform-managed agent consists of three components: 1. **The agent entity.** `nemo agents create` stores the agent YAML as an entity in the workspace. The same configuration can be redeployed without re-registering it. 2. **The deployment controller.** `nemo agents deploy` passes the stored config to the Agents service controller. By default it launches a FastAPI server, assigns a port, watches its health, and tears it down on `nemo agents undeploy`. With `--mode docker` or `--mode k8s` it instead runs the agent as a durable container through the deployments plugin — see [Deploy Agents](/documentation/agents/deploy-agents). 3. **The Agents gateway.** The gateway resolves the agent to its current running deployment and proxies client requests to it, including streaming responses. From a client's perspective, the agent is an OpenAI-compatible endpoint owned by NeMo Platform. Model traffic from inside the agent process routes back through the Inference Gateway, which resolves model entity names to upstream providers and supplies their credentials. This is why agent configs do not carry `base_url` or `api_key` values — the deployment injects the gateway URL automatically, and the gateway looks up the rest. A virtual model is a platform-managed wrapper around one or more backend models. An agent can point at a virtual model entity while the virtual model handles routing, format translation, and [guardrails](/documentation/guardrail-models) behind the scenes — no changes to the agent's YAML required. ### Applying Changes Through Candidate Agents The Agents v2 API has no in-place patch for a stored agent config. When the optimize or secure workflows propose a change — a model swap, a routing split, a guardrailed virtual model — they apply it by creating a sibling agent with the new config, deploying it, and running an evaluation against it. The original agent stays untouched until you decide to promote the candidate. The sibling-candidate pattern is the recommended way to apply changes: you always have a baseline to compare against, and you can roll back by undeploying the candidate. ## Agent Lifecycle Agents are managed end-to-end through the `nemo agents` command group: | Stage | Command | What it does | | --------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Register | `nemo agents create --name --agent-config ` | Store the agent configuration as an `agent` entity in a workspace. | | Deploy | `nemo agents deploy --agent ` | Start a running service from the stored config. | | Wait | `nemo agents deployments wait --agent ` | Block until the deployment is `running` or `failed`. | | Invoke | `nemo agents invoke --agent --input "..."` or `nemo agents invoke --agent-config --input "..."` | Send a single request through the Agents gateway or run a local config directly. | | Optimize | `nemo agents optimize --optimize-config-fileset --optimize-config ` | Run Fabric-backed numeric HPO (Optuna). Stage the bundle first with `nemo agents optimize prepare-fileset`. See [Optimize Agents](/documentation/agents/optimize-agents). | | Tear down | `nemo agents undeploy --agent ` then `nemo agents delete ` | Stop the running service and remove the agent entity. | To run an `agent.yaml` directly without registering it on the platform, pass `--agent-config ` to `nemo agents invoke` or `nemo agents run`. Legacy NAT-only commands: | Stage | Command | What it does | | -------- | ---------------------------------------------------------- | ------------------------------------------------ | | Evaluate | `nemo agents evaluate --eval-config --agent ` | Run a NAT evaluation against the deployed agent. | ## Agent Definition ### Platform-managed agents #### About NeMo Fabric NeMo Fabric gives users one configurable, observable way to run applications across multiple agent harnesses. It standardizes configuration, lifecycle management, and results without requiring a separate integration for every harness. To learn more about Fabric, see [NeMo Fabric](https://docs.nvidia.com/nemo/fabric/about-nemo-fabric/overview/). NeMo Platform uses Fabric as the runtime wrapper around your agent so the platform can deploy it and route its model traffic through shared infrastructure. Intended behavior is recorded in [`ETHOS.md`](/documentation/agents/optimize-agents/ethos). Runtime behavior is described by the platform-managed `agent.yaml`: | Section | Purpose | Example | | ----------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | `config_format` | Selects the versioned Platform agent contract. Use `nemo-agents-spec-v1`. | `nemo-agents-spec-v1` | | `name` | Provides the agent name used in runtime metadata. | `calculator-agent` | | `description` | Summarizes the agent's purpose for users and image metadata. | `Calculator agent executed with DeepAgents` | | `instructions` | Defines shared instructions for every harness. `instructions.system.content` contains the system prompt. | `system.content: You are a concise calculator agent.` | | `default_harness` | Selects the entry under `harnesses` that runs by default. | `deepagents` | | `harnesses` | Declares the supported harness adapters and their harness-specific model or runtime settings. | `deepagents.kind: deepagents` | | `models` | Declares shared named model bindings. A harness uses `models.default` unless it defines its own model. | `default.provider: nvidia`, `default.model: nvidia-nemotron-3-nano-30b-a3b` | | `skills` | Lists skill directories, relative to `agent.yaml`, that are made available to the harness. | `paths: [./skills/math]` | | `mcp` | Configures shared MCP servers that expose tools and resources to the harness. | `servers.github.transport: streamable-http`, `servers.github.url: ${GITHUB_MCP_URL}` | | `tools` | Defines shared tool policy, such as tool names that the harness must block. | `blocked: [shell, browser]` | | `environment` | Configures the agent's runtime workspace, artifacts directory, provider, and provider-specific settings. | `workspace: ./workspace`, `artifacts: ./artifacts` | | `telemetry` | Configures telemetry collection and output, including Relay, ATIF, and ATOF settings. | `provider: relay`, `atif.enabled: true`, `atof.enabled: true` | The calculator agent uses DeepAgents as its harness and the Platform Inference Gateway for model access. It answers arithmetic and numeric comparison requests and records ATIF and ATOF telemetry with NeMo Relay: ```yaml config_format: nemo-agents-spec-v1 name: calculator-agent description: Calculator agent executed with DeepAgents instructions: system: content: | You are a concise calculator agent. Solve arithmetic and numeric comparison requests yourself and return only the answer. default_harness: deepagents harnesses: deepagents: kind: deepagents settings: deepagents: {} models: default: provider: nvidia model: nvidia-nemotron-3-nano-30b-a3b api_key_env: NVIDIA_API_KEY skills: paths: [] mcp: servers: {} tools: blocked: [] environment: workspace: ./workspace artifacts: ./artifacts telemetry: enabled: true provider: relay output_dir: ./artifacts/relay project: calculator-agent atif: enabled: true filename_template: trajectory-{session_id}.atif.json storage: - type: http endpoint: http://localhost:8080/apis/intake/v2/workspaces/default/ingest/atif timeout_millis: 3000 atof: enabled: true filename: events.atof.jsonl mode: append ``` ### NVIDIA Agent Toolkit (NAT) workflows (Legacy) #### About NeMo Agent Toolkit NVIDIA NeMo Agent Toolkit is a flexible, lightweight, and unifying library that allows you to easily connect existing enterprise agents to data sources and tools across any framework. NeMo Platform uses NAT as the runtime wrapper around your agent so the platform can deploy it, evaluate it, optimize it, and route its model traffic through shared infrastructure. For the toolkit itself, see the [NeMo Agent Toolkit documentation](https://docs.nvidia.com/nemo/agent-toolkit/latest/). An agent's behavior is described by a NAT workflow YAML with three top-level sections: | Section | Purpose | Example | | ----------- | ----------------------------------------- | --------------------------------------------------------- | | `functions` | Tools the agent can call | `wiki_search`, `current_datetime`, custom MCP tools | | `llms` | Model bindings the workflow can reference | OpenAI-compatible endpoints, NIM endpoints | | `workflow` | The agent type and its wiring | `react_agent`, `tool_calling_agent`, custom NAT workflows | ReAct is a common agent pattern where the model alternates between a reasoning step and a tool call until it has enough information to answer. It is a good default when you want the agent to decide which tool to use next based on what it has already learned. A minimal ReAct agent looks like this: ```yaml functions: wiki: _type: wiki_search clock: _type: current_datetime llms: llm: _type: openai model_name: nvidia-nemotron-3-nano-30b-a3b workflow: _type: react_agent tool_names: [wiki, clock] llm_name: llm ``` The [Inference Gateway](/documentation/models-and-inference) is the local platform's model proxy. Agents send model requests to it instead of to provider APIs directly, so the platform can resolve model names, attach credentials, and route through middleware on the agent's behalf. Two conventions apply when a config targets a deployed agent: * **Model names use the Inference Gateway entity form**, with slashes and dots converted to hyphens (`nvidia/nemotron-3-nano-30b-a3b` becomes `nvidia-nemotron-3-nano-30b-a3b`). The Inference Gateway resolves the entity to the upstream provider that owns it. * **Leave `base_url` and `api_key` unset on `openai` and `nim` LLMs.** NeMo Platform injects an Inference Gateway URL when it deploys the agent, and the gateway retrieves upstream credentials from the secrets service. Setting `base_url` explicitly bypasses both. ## Common Tasks * [Agent Ethos](/documentation/agents/optimize-agents/ethos): `ETHOS.md`, the durable contract for intended behavior. * [Deploy Agents](/documentation/agents/deploy-agents): run an agent as a local subprocess or as a durable container on Docker or Kubernetes, and invoke it through the Agents gateway. * [Observe Agents](/documentation/agents/observe-agents): ingest and query agent telemetry with NeMo Intake, then review traces, feedback, and evaluator results. * [Optimize Agents](/documentation/agents/optimize-agents): Fabric-backed numeric HPO (`nemo agents optimize`), plus model-routing / skill / prompt suggestions for deployed agents. * [Secure Agents](/documentation/agents/secure-agents): check guardrail coverage and scan recent telemetry for sensitive data. * [Plugins and Skills](/documentation/agents/plugins-and-skills): understand how agent, middleware, and coding-agent integrations extend the local platform. * [Agentic Metrics](/documentation/evaluate-models/metrics/agentic-metrics): evaluate tool use, goal completion, topic adherence, answer accuracy, and trajectories. * [Agent Configuration](/documentation/evaluate-models/metrics/agent-configuration): use agents as online evaluation targets.