Use Cases
- Add human feedback scores to requests
- Record automated evaluation results
- Track custom quality metrics
- Build evaluation datasets for model improvements
Path Parameters
string
required
The unique identifier of the request to evaluate. This is the Helicone request ID returned when logging requests.
Request Body
string
required
Name of the evaluation metric (e.g., “accuracy”, “relevance”, “quality”)
number
required
Numerical score for the evaluation. Can be any number, but typically normalized to a range like 0-1 or 0-100.
Response
Returns a Result object indicating success or failure.null
Null on success
string | null
Error message if the request failed, null on success
Example Request
Example Response
Error Response
Best Practices
- Use consistent evaluation metric names across your requests
- Normalize scores to a standard range (e.g., 0-1)
- Add evaluations soon after request completion for accurate tracking
- Consider using multiple evaluation metrics to capture different quality dimensions
