Developer preview

A lightweight customer CLI, MCP and 45 official task workflows across compute, observability, resources, jobs, generation, evaluations and training.

Start with a useful read

Compare GPU provider observations or inspect published models without an account or API key. Choose CLI, an existing MCP connection, or a direct HTTP request. Public discovery needs no key. The staged Affine batch CLI additionally requires the owner account, an approved qualified runtime, retained request pins and separate execution approval. Other execution retains the existing product gates.

Developer hub — Downloads, official skills and current public availability.

Install the CLI — Node.js 22+, human-readable output and JSON.

Connect MCP — Read-only stdio tools for a compatible host.

Official workflow skills

Skills are task-specific instructions for supported API and MCP workflows. Public reads, scoped account reads and approval-required execution plans are labeled separately. They do not grant permissions or activate execution. Install them into a skills directory recognized by your assistant, or download the individual SKILL.md from the hub.

Install official skills

reliqua skills list --search tokens --category observability
reliqua skills show --skill reliquary-run-token-mix
reliqua skills install --skill reliquary-compute --directory "$HOME/.agents/skills"

Find compute — Compare package costs and source freshness.

Follow published evidence — Inspect public models and network observations.

Availability and compatibility

CLI and MCP release 0.12.0 require Node.js 22 or later. Official skills version 0.12.0 support the preview CLI 0.12.0 and MCP 0.12.0 for the complete catalog; catalog discovery requires MCP 0.5.0 or later. Read the installed command help and registered MCP tool list. The CLI and MCP remain separate artifacts; use either one for a recipe.

The immutable /releases/0.12.0.json manifest contains SHA-256 hashes and byte sizes for both packages and every versioned skill instruction. /developer-preview.json selects the current release; /releases/index.json lists retained releases. Legacy unversioned skill links retain 0.5 instructions. Verify the selected release, not a moving URL. Check the downloaded artifact before installation when verifying a release. Public reads use no credentials. A successful health check does not prove private account access, current capacity or billing qualification. CPU validation and CPU SFT are separate pilot workflows.

Release manifest — Pinned downloads, checksums and compatibility.

API contracts — Actual SDK and OpenAPI coverage.

Execution capabilities — Check account-specific training availability.