Model Pricing
Use the built-in pricing component to configure model pricing catalogs for
cost estimates on managed LLM responses. Relay leaves cost absent when no
configured source matches the provider, model, and token usage.
Configuration
Add the pricing component to plugins.toml. The following configuration
loads a JSON catalog and defines an inline catalog. Relay searches sources in
the listed order, so place overrides before their fallbacks:
Use type = "file" with a JSON catalog path or type = "inline" with the
catalog in plugins.toml. Relay checks sources and catalog entries in listed
order, and it uses the first entry that matches the provider and model.
When Relay merges explicit-or-user, project, and system configuration files, it
prepends higher-priority sources instead of replacing lower-priority sources.
The effective order is system, project, then explicit-or-user. This lets an
enterprise catalog override narrower catalogs while preserving those catalogs
as fallbacks.
Manage Catalog Sources with the CLI
Run the following commands to validate a catalog and add it to project configuration:
Use --user for the user configuration file or --global for
/etc/nemo-relay/plugins.toml. add-source places a new source ahead of
existing sources by default. Use --append to keep it as a fallback.
Verify the Active Configuration
Run the following command to resolve a model against the configured catalogs:
Use nemo-relay doctor to validate configured model pricing sources with the
rest of the gateway configuration. Refer to Add Model Pricing for Cost
Estimates
for the catalog schema, source precedence, and complete CLI workflow.