# Provider menu

`/provider` configures inference capacity that this host sponsors to trusted Omnius instances. `/endpoint` selects the inference endpoint used by your own conversation. The two controls have separate purposes.

The menu uses the existing native terminal modal: keyboard or pointer selection, nested sections, terminal colors, and scrollable content. Configuration and runtime diagnostics stay inside the menu; they are not added to the conversation.

## Configure capacity

Add a source under sponsored models. Choose the managed local Ollama endpoint or an explicitly authorized remote HTTPS provider, then enter its exact model, protocol and endpoint. This operation does not download/load models or deploy a GPU service. Local inference remains subject to the broker and verified accelerator placement.

Set each source's context ceiling, maximum output, concurrent capacity, requests per minute and daily reserved-token budget. A source can be disabled without deleting its policy. Secrets are entered through a masked input or an environment-variable reference and retained in owner-private configuration. Editing an endpoint/protocol clears its previous credential scope.

Requests per minute apply to the source across all allowed requesters over a sliding60-second window. The token budget uses UTC days and conservatively reserves input plus maximum output before dispatch. Cancelled or failed calls can still consume their reservation. Editing limits or restarting does not erase this accounting or the replay ledger.

Configure allowed requester peer IDs separately from outbound sponsor peers. Listen addresses control where this instance accepts encrypted peer connections; relay addresses select explicit circuit relays. The local inference gateway remains authenticated and loopback-only. Only configured models are advertised; endpoint URLs and provider credentials stay on this host.

## Save and run

Changes remain a draft until reviewed and saved. Cancelling discards the draft. If another editor has changed the saved configuration, a stale save is rejected rather than replacing that work.

The overview distinguishes saved configuration from the active runtime revision. Saving does not stop or change a running sponsor. Start, Stop and Apply are deliberate operations; Apply performs a controlled restart after active ownership settles. A runtime started by this terminal is stopped when the terminal exits or hands off an update. An externally started runtime continues after merely closing the menu or terminal; stopping it requires the explicit authenticated Stop action.

Runtime status shows actual state and bounded policy/accounting metadata. Offline, unavailable and pending changes are distinct. `/provider status` opens a separate diagnostic report without printing credentials. `/provider` is a local user control and is not exposed as a REST, gateway or agent-tool mutation.

The [mesh guide](sponsored-inference-mesh.md) describes identity exchange, privacy boundaries, private storage and the equivalent foreground CLI workflow. Provider access restrictions and quotas remain authoritative; denied requests are not retried across sponsor IP addresses.
