For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • About NVIDIA NeMo Relay
    • Overview
    • Architecture
    • Ecosystem
    • Concepts
    • Release Notes
  • Getting Started
    • Agent Runtime Primer
    • Prerequisites
    • Installation
    • Configuration / Setup
    • Quick Start
  • NVIDIA NeMo Relay CLI
    • About
    • Basic Usage
    • Claude Code
    • Codex
    • Cursor
    • Hermes Agent
  • Supported Integrations
    • About
    • OpenClaw Plugin Guide
    • LangChain Integration Guide
    • LangGraph Integration Guide
    • Deep Agents Integration Guide
  • Instrument Applications
    • About
    • Adding Scopes and Marks
    • Instrument a Tool Call
    • Instrument an LLM Call
    • Add Middleware
    • Code Examples
  • Observability Plugin
    • About
    • Configuration
    • Agent Trajectory Interchange Format (ATIF)
    • Agent Trajectory Observability Format (ATOF)
    • OpenTelemetry
    • OpenInference
  • Adaptive Plugin
    • About
    • Configuration
    • Adaptive Cache Governor (ACG)
    • Adaptive Hints
  • NeMo Guardrails Plugin
    • About
    • Configuration
  • Integrate into Frameworks
    • About
    • Adding Scopes
    • Wrap Tool Calls
    • Wrap LLM Calls
    • Handle Non-Serializable Data
    • Using Codecs
    • Provider Codecs
    • Provider Response Codecs
    • Code Examples
  • Build Plugins
    • About
    • Define a Plugin
    • Validate Plugin Configuration
    • Plugin Configuration Files
    • Register Plugin Behavior
    • Design Plugin Configuration
    • NeMo Guardrails Example Plugin
    • Code Examples
  • Contribute
    • About
    • Development Setup
    • Workflow and Reviews
    • Testing and Documentation
  • Reference
    • APIs
      • Python Library Reference
      • Node.js Library Reference
      • Rust Library Reference
        • nemo-relay
        • nemo-relay-adaptive
          • acg
            • anthropic_plugin
            • canonicalize
            • capability
            • ir_builder
            • openai_plugin
            • passthrough
            • plugin
              • PluginInput
              • PluginOutput
              • ProviderPlugin
            • plugin_registry
            • policy
            • profile
            • prompt_ir
            • retention
            • stability
            • telemetry
            • types
            • variable_extractor
            • error
            • MIN_ACG_OBSERVATIONS
          • acg_component
          • acg_learner
          • acg_profile
          • adaptive_hints_intercept
          • cache_diagnostics
          • config
          • context_helpers
          • drain
          • error
          • intercepts
          • learner
          • plugin_component
          • redis
          • storage
          • subscriber
          • tool_parallelism_learner
          • trie
          • types
          • AdaptiveRuntime
        • nemo-relay-ffi
    • Performance
  • Resources
    • Support and FAQs
    • Glossary
    • Troubleshooting Guide
    • Community
    • Legal
NVIDIANVIDIA
Developer-friendly docs for your API
Privacy Policy | Your Privacy Choices | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026, NVIDIA Corporation.

LogoLogo
On this page
  • Design
  • Structs
  • Traits
ReferenceAPIsRust Library Referencenemo-relay-adaptiveacg

Module plugin

||View as Markdown|
Previous

Struct Passthrough Plugin

Next

Struct Plugin Input

Generated from cargo doc --no-deps -p nemo-relay -p nemo-relay-adaptive -p nemo-relay-ffi.

Provider plugin trait and input/output types for the Adaptive Cache Governor (ACG) system.

The ProviderPlugin trait defines the contract between ACG’s provider-agnostic optimization pipeline and backend-specific translation logic. Plugins receive a PluginInput containing the original request, Prompt IR, intent bundle, and agent identity, and produce a PluginOutput with the translated request and a TranslationReport.

Design

  • Synchronous: translate is a pure data transform (JSON restructuring), not an I/O operation. This matches the LlmCodec pattern in crates/core/src/codec/traits.rs.
  • Compatibility facade: provider plugins keep their existing synchronous trait surface, but can internally split translation into semantic hint planning plus request-surface application.
  • Send + Sync: Required for storage as Arc<dyn ProviderPlugin> in concurrent contexts.
  • Object-safe: The trait is designed to be used as a trait object.

Structs

  • PluginInput: Input data provided to a plugin for translation.
  • PluginOutput: Output produced by a plugin after translation.

Traits

  • ProviderPlugin: Provider plugin trait for backend-specific translation.