Validate an owned JSONL dataset
Upload one bounded owned JSONL input and submit an explicitly approved CPU validation specification without paid provisioning.
What you get
An owned bounded CPU validation job tied to an immutable approved dataset receipt.
Bounded CPU pilot only; current feature gate, account grant, fresh worker and two exact approvals remain necessary.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | qualified pilot |
| Credential corridors (see workflow) | resources |
Ask your assistant
Example task
Validate this small dataset on CPU after I approve its upload and bounded job.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-cpu-validate
reliqua skills install --skill reliquary-cpu-validate --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 jobs_capabilities and confirm current permission, submission grant and fresh qualified worker availability. This bounded CPU workflow provisions no paid capacity and does not qualify training.
- Confirm rights and explicit authorization to upload the exact UTF-8 JSONL content, at most 32768 bytes, in instruction, preference or corpus format. Call job_input_upload with rightsConfirmed:true, approveExecution:true and a stable caller-supplied UUIDv4 idempotencyKey.
- Review the immutable dataset receipt: dataset ID, SHA-256, size_bytes and format. Present the exact dataset_validation spec, deadline_seconds from 60 to 3600 and max_attempts from 1 to 3 for separate execution approval.
- After approval call job_submit with that spec, approveExecution:true and its own stable UUIDv4 request key. Preserve both upload and submission keys independently; never reuse one key for a different operation or input.
- On an unknown outcome retain exact inputs, original key and any returned job ID. Do not silently retry, poll, enroll workers, provision paid compute or widen the workload.
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_jobs_capabilities |
| MCP | reliquary_job_input_upload |
| MCP | reliquary_job_submit |
| HTTP | GET /api/v1/jobs/capabilities |
| HTTP | POST /api/v1/job-inputs |
| HTTP | POST /api/v1/jobs |
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.