Order an approved dataset
Submit one exact generation quote after approval, preserving its cost ceiling and request identity.
What you get
One submitted order or a precise refusal/unknown outcome with its original request identity.
Execution requires a fresh server quote, explicit approval, credits and current generation gates.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | gated |
| Credential corridors (see workflow) | orders |
Ask your assistant
Example task
Place the dataset order from this quote after I approve its exact cost and limits.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-order
reliqua skills install --skill reliquary-generation-order --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
- Verify the current generation catalog and registered write tool. Obtain the full server quote; show its quote ID, selected inputs, maximum cost, expiry and limitations before the user approves execution.
- After explicit approval of that exact unexpired quote, call reliquary_generation_order with quote_id, approveExecution:true and one stable caller-supplied idempotencyKey of 16-80 letters, digits, underscores or hyphens.
- The call may reserve or spend credits and enqueue work. Preserve the returned order identity and separate accepted/queued execution from delivery and billing settlement.
- For an ambiguous result, keep the exact quote and original request key. Do not silently retry, create a new key, batch purchases or order from an expired/different quote.
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_catalog |
| MCP | reliquary_generation_order |
| HTTP | GET /api/v1/generation/catalog |
| HTTP | POST /api/v1/dataset-orders |
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.