Compare declared GPU participation
Compare public GPU model participation and qualified quality windows while preserving declarations, unavailable metrics and source clocks.
What you get
A bounded declared-fleet comparison with qualified metrics and explicit unknowns.
Documented public read workflow; stored availability, source freshness and metric qualification still apply.
| Support | Requirement |
|---|---|
| Interfaces | CLI, MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
Which declared GPU models are participating, and is their quality comparison qualified?Install this skill
Use an existing compatible MCP connection or the customer CLI. Skills provide instructions; installing them does not configure credentials, grant permissions or enable execution.
Install reliquary-run-gpu-fleet
reliqua skills install --skill reliquary-run-gpu-fleet --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.6.0.
Install the customer CLI — Verified release downloads, commands and troubleshooting.
Connect MCP — Keep writes disabled for discovery and planning.
Authentication and exact scopes — Corridor names identify key configuration; the API checks its actual read and write scopes.
Follow the workflow
- Read the selected public run snapshot once and inspect its declared GPU fleet, available card metrics, observation windows and source timestamps.
- Label GPU model and device counts as miner declarations. Missing card-window mappings, token shares, rejection rates or correspondence remain unknown, never zero.
- Compare only qualified, compatible cohorts in the returned time window; preserve sample counts and aggregation meanings. A declared card label is not hardware attestation or a causal performance comparison.
- Report what is observed, what remains unqualified and the timestamps. Do not provision workers, rent GPUs, change miners or infer chain settlement from telemetry.
Tools and API routes
Call reliquary_connection first and use only tools registered in that connection. Route templates need the owned resource identifiers described by the existing API reference.
CLI read
reliqua runs inspect --json| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_run_monitor |
| HTTP | GET /api/monitoring/run |
Availability and authorization
A successful read does not grant execution access or establish qualified capacity. Preserve source clocks, missing values, account ownership and the limits of the returned evidence.
Back to the skills catalog — Find another workflow or connect an interface.