Compute
Compute reference
The reference section for Lithi Compute. Work operations, management resources, schemas, limits, formats, states and versions, plus the authority that publishes each fact.
What this section covers
Reference pages carry exact facts and no walkthrough. Five kinds of fact live here, and they are kept apart on purpose.
Work operations quote, admit and return work. Management resources configure your organization. Schemas describe the shapes you send and receive. Limits bound one request. Errors are published per operation, never as one global list.
The reference pages
- Work API operations — quote, run, batch, status, result, artifacts and cancellation
- Management API resources — the thirteen resource families and their shared lifecycle
- Schemas — TaskSpec, Job and ResultBundle, narrowing and unknown fields
- Limits — body, artifact, item, batch, token, concurrency, rate, budget and retention
- Formats — the versioned format subsets Lithi reads and writes
- States — every public wire value, its terminal rule and its next action
- Versioning — six version lines and what breaks
- Changelog — how to read a change entry
- Migration guide — moving to a new version safely
Which authority publishes each value
| Fact you need | Authority that publishes it |
|---|---|
| Base URL, current API version, your key's scopes | Developer settings in the portal |
| Operation paths, request and response shapes | The API description you download from the portal |
| Per-operation refusals | That operation's generated error schema |
| Workflow parameters, item ceiling, output schema | The workflow descriptor |
| The most you can be charged | Your quote |
| Retention for one result bundle | That bundle's result-manifest.json |
| The name and version of a released client | The client page for that language |
No reference page overrides those authorities. Where a page and a generated authority differ, the generated authority is correct, and the page is stale.