API keys
| Project | Failover chain | Actions |
|---|
People
Who can use HOIV Chat, on which chains, within which limits, and until when.
| Person | Access | Used today | Actions |
|---|
People sign in to HOIV Chat with their HOIV account, so each needs theirs linked here. Suspend stops their access at once and keeps everything, to resume later. Revoke deletes their access and their conversations, for good. Limits are counted per UTC day and month, as for every key.
Providers
| Provider | Command or endpoint | Credentials | Actions |
|---|
Usage & cost
Requests per day
By project
| Project | Requests | Errors | Cost | In / Out tokens |
|---|
By provider
| Provider | Requests | Errors | Cost | Time spent |
|---|
Recent requests
| When | Project | Provider / model | Outcome | Time | Cost |
|---|
Failures
Wall clock burnt without producing anything. A provider that times out is expensive even though it never returns a token.
| Provider | Kind | Count | Time burnt |
|---|
Stats
The last 12 months
Requests per day
Show the days as a table
Top models
The model that actually answered, where the ledger recorded it.
Top callers
Every request a service sent, failures included.
Providers
Who served the requests that succeeded.
Where the tokens went
When it happens
Show the hours as a table
Provider health
Is each leg answering?
| Provider | State | Last answered | Last failure |
|---|
Sidelined right now
A provider or credential that fails is sidelined on an exponential ladder, and a success clears the record; its legs are marked amber in API keys meanwhile. An empty table means nothing is sidelined, which is not the same as everything answering: a failure that is not the provider's fault is never sidelined. The table above says whether a leg works.
| Scope | Target | Strikes | Cooldown remaining |
|---|