Adaptive Hints
Use Adaptive Hints when downstream model calls or provider adapters can safely receive guidance metadata from the adaptive runtime.
Adaptive hints register as LLM request intercepts. Lower numeric priority values run earlier in the intercept chain. The default priority is chosen relative to other middleware rather than as a standalone importance score.
plugins.toml Example
This configuration injects adaptive guidance into outgoing model requests while allowing later request intercepts to continue running.
Plugin Configuration
Use plugin configuration when the application should let NeMo Relay own the Adaptive Hints request-intercept lifecycle.
Python
Node.js
Rust
Manual API
Use the manual runtime API when an integration needs to own adaptive lifecycle directly instead of activating the top-level plugin component.
Python
Node.js
Rust
Fields
Disable break_chain unless the adaptive hint should be the final request
transform. Adjust priority only when adaptive hints need to run before or
after known application middleware.
Expected Output
Outgoing managed LLM requests receive adaptive hint metadata in the configured header and body location. The hints do not replace the application callback or change the returned value by themselves. Downstream code must explicitly interpret the metadata before behavior changes.
Common Validation Failures
- Unknown adaptive hint fields when unknown fields are treated as errors.
inject_body_pathdoes not match the request shape expected by downstream provider adapters.- Hint injection is enabled before downstream model paths can consume or ignore the metadata safely.