> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://docs.nvidia.com/dynamo/llms.txt. For full content including API reference and SDK examples, see https://docs.nvidia.com/dynamo/llms-full.txt.

# Agents

Dynamo provides a small set of request extensions and trace utilities for
serving agentic workloads. The harness remains responsible for the semantic
agent trajectory. Dynamo receives lightweight metadata and uses it for serving
telemetry, routing hints, and backend-specific cache behavior.

## Core Concepts

| Concept | Purpose |
|---------|---------|
| [Agent Tracing](/dynamo/v1.1.1/user-guides/agents/agent-tracing) | Passive `session_id`/`trajectory_id` metadata plus Dynamo-owned request timing, token, cache, worker-placement, and harness tool-event traces. |
| [Agent Hints](/dynamo/v1.1.1/user-guides/agents/agent-hints) | Optional per-request hints such as priority, expected output length, and speculative prefill. |
| [Tool Calling](tool-calling.md) | Supported tool-call parsers and parser names. |
| [Reasoning](reasoning.md) | Supported reasoning parsers for chain-of-thought models. |
| [Chat Processors](chat-processor-options.md) | Dynamo, vLLM, and SGLang preprocessing options. |

## Backend-Specific Guides

Agent features are exposed through common request metadata, but backend support
varies by runtime.

| Backend Guide | Contents |
|---------------|----------|
| [SGLang for Agentic Workloads](/dynamo/v1.1.1/user-guides/agents/sg-lang-for-agentic-workloads) | Priority scheduling, priority-based radix eviction, speculative prefill, and streaming session control for subagent KV isolation. |

## Request Surface

Agent-facing request metadata lives under `nvext` on OpenAI-compatible request
bodies:

```json
{
    "nvext": {
        "agent_context": {
            "session_type_id": "deep_research",
            "session_id": "research-run-42",
            "trajectory_id": "research-run-42:researcher"
        },
        "agent_hints": {
            "priority": 5,
            "osl": 1024
        }
    }
}
```

Use `agent_context` when you want traceability across LLM calls, tool calls, and
external trajectory files. Use `agent_hints` only when the harness has
serving-relevant intent that Dynamo can act on.

> Agent-aware serving features in Dynamo

## Docs

- [Agent Tracing](https://docs.nvidia.com/dynamo/v1.1.1/user-guides/agents/agent-tracing.md): Attach trajectory identity and export Dynamo request and tool-event telemetry
- [Agent Hints](https://docs.nvidia.com/dynamo/v1.1.1/user-guides/agents/agent-hints.md): Per-request serving hints for agentic workloads
- [SGLang for Agentic Workloads](https://docs.nvidia.com/dynamo/v1.1.1/user-guides/agents/sg-lang-for-agentic-workloads.md): Priority scheduling and session control for multi-turn agentic serving