> This page is for NeMo Relay, version v0.10.0.
> For other versions, use one of these documentation indexes:
> - Latest (v0.10.0) (default): https://docs.nvidia.com/nemo/relay/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/relay/dev/llms.txt
> - v0.10.0: https://docs.nvidia.com/nemo/relay/v0.10.0/llms.txt
> - v0.9.4: https://docs.nvidia.com/nemo/relay/v0.9.4/llms.txt
> - v0.8.4: https://docs.nvidia.com/nemo/relay/v0.8.4/llms.txt
> - v0.7.3: https://docs.nvidia.com/nemo/relay/v0.7.3/llms.txt
> - v0.6.0: https://docs.nvidia.com/nemo/relay/v0.6.0/llms.txt
> - v0.5.0: https://docs.nvidia.com/nemo/relay/v0.5.0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/relay/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/relay/_mcp/server.

# APIs

Use these generated library references for symbol-level API documentation.

Use the generated reference when you already know which public symbol you need.
Generated reference pages do not explain these runtime details:

* Ownership
* Managed execution ordering
* Cleanup boundaries
* Middleware behavior
* Support boundaries

For those topics, start with [Concepts](/about-nemo-relay/concepts), the
[Agent Runtime Primer](/about-nemo-relay/agent-runtime-primer), or the
workflow-specific documentation path that matches the boundary you own.

The primary bindings have these references:

* [Python Library Reference](/reference/api/python-library-reference)
* [Node.js Library Reference](/reference/api/nodejs-library-reference)
* [Rust Library Reference](/reference/api/rust-library-reference)

For resource snapshot behavior and configuration across bindings, refer to
[Resource Metrics](/configure-plugins/resource-metrics).