Create an Evaluator or update it with a new version if it already exists.
Evaluators are identified by the ID or their path. The spec provided determines the version of the Evaluator.
If you provide a commit message, then the new version will be committed; otherwise it will be uncommitted. If you try to commit an already committed version, an exception will be raised.
Path of the Evaluator, including the name. This locates the Evaluator in the Humanloop filesystem and is used as as a unique identifier. For example: folder/name or just name.
ID for an existing Evaluator.
Message describing the changes made.
Successful Response
Path of the Evaluator including the Evaluator name, which is used as a unique identifier.
Unique identifier for the Evaluator.
Name of the Evaluator, which is used as a unique identifier.
Unique identifier for the specific Evaluator Version. If no query params provided, the default deployed Evaluator Version is returned.
An enumeration.
The number of logs that have been generated for this Evaluator Version
The number of logs that have been generated across all Evaluator Versions
Inputs associated to the Evaluator. Inputs correspond to any of the variables used within the Evaluator template.
ID of the directory that the file is in on Humanloop.
Message describing the changes made.
The list of environments the Evaluator Version is deployed to.
The user who created the Evaluator.
The user who committed the Evaluator Version.
The date and time the Evaluator Version was committed.
Evaluators that have been attached to this Evaluator that are used for monitoring logs.
Aggregation of Evaluator results for the Evaluator Version.
Additional fields to describe the Evaluator. Helpful to separate Evaluator versions from each other with details on how they were created or used.