Inventory & catalogs

Read discovery metadata without confusing reference templates with qualified offerings.

GET /api/inventory

Returns schemaVersion: 1, a revision, fetchedAt, sources, objects, and an optional generation catalog. The projection combines explicit metadata from published tasks, published checkpoints, and the qualified generation catalog.

Object fieldMeaning
kindtask, environment, model, or dataset.
lifecycleactive, retired, qualified, or published.
sourceIdIdentity of the associated entry in sources.
taskId, modelId, revision, environmentId, datasetIdPublished identities; null when unknown.
capabilities.configureWhether configuration is exposed for this object.
capabilities.orderWhether the current inventory exposes ordering capability.
detailsPublished label/value metadata.

GET /api/catalog

Returns workspace examples with source: examples, approved execution-profile definitions, and the reference training catalog. Use these to render or prepare configurations.

Reference offer prices and model choices are not live provider inventory. Use /api/compute/catalog for GPU comparison and /api/capabilities in the browser session for executable training availability.

GET /api/v1/generation/catalog

Returns ordering, any_model_ordering, models, envs and architectures. Each model has an id, name, optional pinned model identity, optional price_per_mtok_usd, and compatible sources. Sources and environments expose id, name, prompts_available, and thinking. architectures lists the model architectures (config.json architectures[0]) that pinned-model, Batch API and evaluation quotes accept, or is null before the list was first read.

Catalog-order bodies use model and source IDs from this response. Pinned-model bodies use a public model repository, full commit revision, and an env ID. Keep these request modes separate.

Inspect generation availability

const response = await fetch('https://api.reliqua.ai/api/v1/generation/catalog');
if (!response.ok) throw new Error('Catalog request failed: ' + response.status);
const catalog = await response.json();
console.log('Catalog orders:', catalog.ordering);
console.log('Pinned-model orders:', catalog.any_model_ordering);
console.table(catalog.models.flatMap((model) => model.sources.map((source) => ({
  model: model.id,
  source: source.id,
  promptsAvailable: source.prompts_available,
  thinking: source.thinking,
}))));

GET /api/v1/capacity

Public, no key. Whether an order on a model not yet running would start now: state is available, queued (every place for a new model is taken) or daily_capacity_reached (today’s capacity is used; daily_capacity_resets_at gives the next midnight UTC). It also returns queued_orders and running_orders (counts over all customers), estimated_start_at for a new order (an estimate, or null) and observed_at. The answer is refreshed at most every 30 seconds. To know whether your model starts at once (an order on a model already running never waits in line), read capacity on its quote.

Batches, dataset orders and evaluations share this capacity and one first-in, first-out line. An order that has not started after 24 hours in line is released in full. Quotes carry the same answer for their model in capacity; see Capacity and queueing in the Batch API reference.

Capacity · public read

curl --fail-with-body --silent --show-error \
  'https://api.reliqua.ai/api/v1/capacity'

Other catalogs

Evaluation catalog — Qualified held-out sets and quote limits.

Compute catalog — Provider offer fields and price units.

Dataset orders — Use the generation catalog in a quote-first order flow.