Runnable engines
96of 128
Priced engines
106
Dispatched jobs
0
GPU utilisation
—
Control plane
GET https://app.epitorix.com/api/v1/health — from your browser, right now
probing…
GET https://app.epitorix.com/api/v1/pricing
probing…
Job submission
The submit path is wired to the real control plane. Pressing this sends an unauthenticated request and shows the server's actual answer. It cannot dispatch work and cannot move a credit, because the API refuses an anonymous caller — which is the correct behaviour, not a bug to route around.
Campaign graph
No campaign planned yet. Tell the orchestrator what to bind and this graph draws the plan it composes.
GPU and memory utilisation
GPU and RAM utilisation are NOT displayed. No endpoint on the control plane reports them, so any gauge here would be decoration.
What would make it realA telemetry endpoint exposing real worker utilisation and queue depth. None exists — confirmed twice, independently. Note that GET /api/v1/admin/telemetry is NOT it: it is admin-only and returns per-action latency baselines, so wiring a gauge to it would put a plausible number under the wrong label. Until a real endpoint exists a utilisation gauge would be a fabricated metric rendered as motion.
Job status
No jobs. Nothing has been dispatched from this deployment, so there is nothing to report — this table stays empty rather than showing an example row.