The Providers screen in the inference console shows where your models run. Afterburner serves only clutch-layers models, on model servers that FirstByte runs. The screen has no vendor rows. It lists the models that the router sends traffic to. It answers one question: “which models are routed now, and does their address answer?” The screen does not store or edit credentials. Provider keys and GPU capacity are on Compute › GPUs. The Manage GPU provider keys button on the screen opens that tab.

​
What the screen lists

The screen calls one procedure, models.local, and shows the routed models in a table. This is the same registry that the Models screen shows. Each row has these columns: The search box filters the rows by name, weights path, engine, and namespace. The count beside it shows the rows that match against all rows. The screen has these states:

​
Reading the Upstream pill

The Upstream pill describes the address that the model routes to. It does not describe the registry entry. The verdict comes from real turns. It is not a probe. An endpoint that nobody has called reads untried. The screen has no separate connectivity test. Routing failures also show in agent runs and in the telemetry of the fabric. See Telemetry.

​
Adding a model and adding capacity

The Providers screen has no write path. Use these screens instead: Powerful, long-lived credentials stay on the surface that owns them. The operator console reads names and states only. See Authentication.