Performance & history
Read provider attempts, completion outcomes, latency, and reported usage without treating estimates as earnings.
Open My computers and select an enrolled computer to review its current state and observed activity.
Time windows
Provider statistics support 7-day and 30-day views. History can be filtered by model and outcome, then paginated through older attempts.
Attempt outcomes
| Outcome | Meaning |
|---|---|
completed | The provider reported a normal terminal result and usage. |
provider_failed | The runtime reported an inference failure. |
caller_canceled | The developer connection ended before completion. |
interrupted | The assignment ended without a normal completion path. |
Measurements
History can include total duration, time to first output, prompt tokens, completion tokens, and a terminal error. Missing values mean the measurement was not reported; they do not mean zero.
Percentiles and averages describe observed attempts inside the selected window. They are useful for diagnosing changes, but they are not uptime guarantees or model-quality scores.
Usage is provider-reported
The provider runtime reports token counts after inference. Router validates protocol bounds and stores the observation. It cannot independently prove that the runtime’s token count is exact.
Diagnose a change
- Narrow the history to one model and time window.
- Compare completion rate and first-output timing before and after the change.
- Open failed attempts and group them by terminal error.
- Check whether missing usage increased separately from zero-token responses.
- Correlate the time with local Core Node logs and resource pressure.
Use provider troubleshooting for state-specific recovery.