You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
@pipelex/sdk on npm
Added
checkModelReference: client.checkModelReference(reference, category?) asks the runner whether one model reference resolves, as what kind and to which model (GET /v1/models/check, served by pipelex-api from pipelex 0.78.0 and on the hosted API), and returns the typed ModelReferenceVerdict, whose kind narrows its matches; a reference that resolves nowhere is a not_found verdict carrying the names the caller may have meant, and one the runner cannot read is an ApiResponseError whose errorType is InvalidModelReference or InvalidModelCategory. docs/architecture.md describes it.
pipelex-sdk on PyPI
Added
check_model_reference: client.check_model_reference(reference, category=...) asks the runner whether one model reference resolves, as what kind and to which model (GET /v1/models/check, served by pipelex-api from pipelex 0.78.0 and on the hosted API), and returns the typed ModelReferenceVerdict from the new pipelex_sdk.model_reference_models, one arm per reference kind so that narrowing it types its matches; a reference that resolves nowhere is a NOT_FOUND verdict carrying the names the caller may have meant, and one the runner cannot read raises ApiResponseError whose error_type is InvalidModelReference or InvalidModelCategory. docs/architecture.md describes it.