Inspect a dataset order
Read owned generation orders and explain progress, delivery and refund state without polling.
What you get
An owned order status with progress, delivered-file metadata and billing distinctions.
Requires the configured scope and current account permission; this label does not establish execution capacity.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | authenticated read |
| Workflow state | available |
| Credential corridors (see workflow) | orders |
Ask your assistant
Example task
What happened to my dataset order, and has it delivered?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-generation-track
reliqua skills install --skill reliquary-generation-track --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
- Use a supplied order ID with reliquary_generation_order_get. If the user needs help identifying it, list recent owned orders with reliquary_generation_orders and choose the relevant returned ID.
- Report actual lifecycle state, progress, delivery metadata and any returned refund/billing amounts. A queued order is not delivered; delivery does not prove finalized network rewards.
- Read another status only for an explicit progress request. If a separate credit reconciliation is needed, use generation_balance rather than deriving the ledger from progress.
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_generation_orders |
| MCP | reliquary_generation_order_get |
| HTTP | GET /api/v1/dataset-orders |
| HTTP | GET /api/v1/dataset-orders/{id} |
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.