Create Eval Config
POST/eval-configs
Create a new eval config in the given workspace.
The payload (content JSON dict or content_yaml string) is validated against the
eval config schema before being stored, and normalised so extra fields are dropped and
defaults filled in. Caller must be a platform admin or a workspace admin/editor. The config
name must be unique among live (non-deleted) configs in the workspace; a concurrent create
racing to the same name is rejected rather than silently overwriting the other.
Request
Responses
- 201
- 403
- 404
- 409
- 422
Successful Response
Forbidden
Not Found
Conflict
Unprocessable Entity