Compare retained network history
Compare published network-wide observations over a supported 24-hour, 7-day or 30-day range.
What you get
A dated historical comparison with visible retention and coverage gaps.
Documented read workflow; source freshness and current service state still apply.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | public read |
| Workflow state | available |
| Credential corridors (see workflow) | None |
Ask your assistant
Example task
Compare the published network history over the last seven days and show gaps.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-network-history
reliqua skills install --skill reliquary-network-history --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.5.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
- Call reliquary_monitoring_history with a supported view: network, miners, chain or status; choose range 24h, 7d or 30d to match the request. HTTP uses the same range query parameter.
- Preserve source timestamps and documented units. Retained observations can be partial; do not fill missing intervals with zero or infer a continuous healthy service from sparse points.
- Compare like-for-like metrics over the returned window. Distinguish observed activity, accepted work, settlement and model improvement.
- Use a single bounded read for the requested range; do not start recurring monitoring.
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.
| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_monitoring_history |
| HTTP | GET /api/monitoring/history/{view} |
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.