27 August 2026
Managed teacher sources
Distill sources can select a teacher from the model catalog without storing a provider key. Managed proxy calls record the requested and served models and bill the workspace balance at the catalog's per-token rates; test-mode calls record cost without a charge.
Connection type and model picker
New loops default to a Lizzy-managed connection with searchable per-million-token pricing. Existing managed sources can switch models, while BYOK sources can rotate their provider URL and key.
15 August 2026
From endpoint tour to implementation guide
Added authentication, core concepts, a complete tutorial, webhook handling, lifecycle guides, example responses, state machines, and failure-specific recovery steps.
Readable, copyable code examples
Examples now use language-aware syntax highlighting, accessible language tabs, and copy controls. Broken continuation markers were removed from shell commands.
Data schemas aligned with runtime
Distill source schemas no longer collide with knowledge-source components. Upload formats, dataset filters, and holdout split fields now describe the values accepted by the service.
Request IDs are returned consistently
Control-plane responses now carry a non-empty X-Request-Id that matches the structured error envelope when a request fails.
Resumable Pilot workflows
Pilot workflows persist phase, blockers, resource references, watches, human handoffs, and resume or abandon state instead of rediscovering the same work every turn.
Validated plan provenance
Clients can bind a live run to a succeeded live-mode dry run and its exact plan hash. Pilot requires this safer path before proposing live spend.
Resumable connector pulls
Connector imports expose a persistent pull ID, progress, row count, output version, and failure object, including successful zero-row imports.
Compatibility policy
JSON control-plane changes are additive whenever possible. Existing direct REST clients may still omit validated_dry_run and plan_hash on live run creation; new integrations should provide both. Pilot treats them as required safety evidence.
Unknown response fields should be ignored. Mutation clients should reject or flag unknown request fields before sending them, pin the dated API behavior they were tested against, and diff the OpenAPI document during upgrades. A semantic or removal change receives a dated migration note here.
Stay informed
Check this page before upgrading generated clients or production automation. In CI, fetch the OpenAPI 3.1 document, compare it with your approved snapshot, and require a human review for changed mutations, enums, security boundaries, or terminal states.
Webhook consumers should subscribe to the narrowest event patterns they need and retain unknown event types safely. Agent integrations should pin a tool-contract version per workflow so a deployment cannot alter the meaning of an in-flight checkpoint.