Cancel a dataset order
Request cancellation of one owned generation order after showing current progress and refund uncertainty.
What you get
A cancellation request result with honest remaining work and refund status.
Requires order ownership, explicit cancellation approval and current server support.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | gated |
| Credential corridors (see workflow) | orders |
Ask your assistant
Example task
Cancel my dataset order after reviewing what can still stop and be refunded.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-cancel
reliqua skills install --skill reliquary-generation-cancel --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
- Read the exact owned order, current state and returned refundable amounts. Explain that the platform decides what work can stop and which credits can be refunded.
- Obtain explicit approval for cancellation of that order, then call generation_cancel with its ID and approveExecution:true. This operation has no client idempotency-key field; do not invent one.
- Report the resulting server state and any remaining work or billing. On an ambiguous result inspect owned state before deciding whether another mutation is appropriate; do not silently repeat cancellation.
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_order_get |
| MCP | reliquary_generation_cancel |
| HTTP | GET /api/v1/dataset-orders/{id} |
| HTTP | POST /api/v1/dataset-orders/{id}/cancel |
Availability and authorization
This workflow can prepare an action using existing contracts. Execution requires current server capabilities, qualified capacity, appropriate account scope, a fresh quote when applicable, and explicit approval of the concrete action. The customer preview CLI has no execution commands; MCP writes stay disabled by default.
Back to the skills catalog — Find another workflow or connect an interface.