Serving controls
Choose what a computer serves and stop participation when you need to.
Provider participation is explicit. Enrolling a computer identifies it to Router; serving controls whether it should accept developer requests.
Choose a model
Select one Router-supported model appropriate for the computer. The chosen model ID and revision must match the current Router catalog. A model installed locally but absent from the enabled Router API is not eligible for assignments.
Start serving
Enable serving in the supported Core Node flow and keep the application running. Router reports readiness only after it observes a valid provider session and the matching model.
Pause or stop
Stop serving before maintenance, model changes, or shutting down the computer. Core Node stops claiming new work and reports the state change. If a request is already running, allow it to finish when practical or expect the developer to receive an interrupted response.
Control public discovery separately
Profile and offer publication controls public visibility and new manual selection. Unpublishing does not stop Serving or remove otherwise eligible capacity from Auto. It leaves accepted requests under their saved quotes. To stop accepting work, use Serving controls.
Revoke a computer
Revocation removes the Router enrollment and prevents that device from participating with the old provider identity. Use it when a computer is retired, transferred, or no longer trusted.
Blocking requests or removing a computer withdraws Router access and can interrupt active work. Blocking requires known serving settings; pause any active schedule and wait for unfinished start or settings changes. It is different from graceful Pause serving. Starting serving in Core Node can allow requests again. Check the saved and observed states separately after a change.
Operational checklist
- Use a stable network connection and power source for longer sessions.
- Keep enough local resources available for the selected model.
- Apply model or Core Node updates before returning to ready state.
- Pause serving before restarting the runtime or changing model files.
- Check observed status after every configuration change.
Review readiness and states to interpret what Router reports.