Skip to main content
The model catalog is the set of models available through the HUD inference gateway. An evaluation selects models by their catalog API name, so swapping the model changes nothing about the taskset or environment. Open Models to search the catalog, filter to trainable or private models, and copy the API name used by the SDK.

​
Public and team models

Models shown in the evaluation dialog have an available checkpoint. A single evaluation can select several models and run each one against the same taskset.

​
Read a model page

The exact provider route is an implementation detail of the catalog entry. Use the model’s API name in the SDK and let the gateway resolve the active route.

​
Create a trainable model

Select New model, choose a trainable base model, and give the fork a name. The new team-owned model inherits the source model’s base weights or its currently promoted checkpoint, then starts its own checkpoint history. Creating the model does not train it. Use the TrainingClient to collect rollouts, apply updates, and promote checkpoints behind the same model API name.

​
Credentials and cost

A HUD_API_KEY authenticates gateway requests and attributes usage to your active team. Provider credentials configured under BYOK can route eligible requests through your own provider account. See team settings for keys, usage, and limits. With a model selected, run it against a fixed suite in evaluations.