Helicone doesn’t run evaluations for you—we provide a centralized location to report and analyze evaluation results from any framework, giving you unified observability across all your evaluation metrics.
Why Use Scores
Centralize Evaluation Results
Report scores from any evaluation framework for unified monitoring and analysis
Track Performance Over Time
Visualize how accuracy, hallucination rates, and other metrics evolve
Compare Experiments
Evaluate different prompts, models, or configurations with consistent metrics
Catch Regressions
Monitor metric trends to detect when changes negatively impact quality
Quick Start
1
Make a request and capture the ID
Make your LLM request through Helicone and capture the request ID:
2
Run your evaluation
Use your evaluation framework or custom logic to assess the response:
3
Report scores to Helicone
Send evaluation results using the Helicone API:
4
View analytics
Analyze evaluation results in the Helicone dashboard to track performance trends, compare experiments, and identify areas for improvement.
API Format
Request Structure
The scores API expects this format:Score Values
| Type | Description | Example | |------|-------------|---------|| |integer | Numeric scores (no decimals) | 92, 85, 0 |
| boolean | Pass/fail or true/false metrics | true, false |
Multiple Scores
You can report multiple metrics in a single API call:Integration Examples
RAGAS (RAG Evaluation)
Evaluate retrieval-augmented generation for accuracy and hallucination:LLM-as-Judge
Use a strong model to evaluate responses from another model:Custom Evaluation Logic
Implement domain-specific evaluation metrics:Automated Evaluation Pipeline
Automatically evaluate all requests using webhooks:Viewing and Analyzing Scores
Dashboard Analytics
Helicone provides several ways to analyze your scores:- Request-level scores: View scores for individual requests in the request detail page
- Aggregate metrics: See average, min, and max scores across all requests
- Score distributions: Understand the spread of scores with histogram visualizations
- Time-based trends: Track how scores change over time
- Filtering: Filter requests by score ranges (e.g.,
accuracy > 90)
Querying Scores via API
Retrieve score analytics programmatically:Use Cases
RAG Application Monitoring
Track retrieval-augmented generation quality over time:Model Comparison
Compare different models on the same evaluation dataset:A/B Testing
Test prompt changes before full rollout:Best Practices
Use Consistent Metrics
Define standard metrics across your team and use them consistently
Convert Decimals
Always convert decimal scores (0-1) to integers (0-100) before reporting
Name Clearly
Use descriptive score names like
answer_relevancy not score1Track Context
Use custom properties to segment scores by feature, model, or experiment
Automate Evaluation
Set up automated evaluation pipelines rather than manual scoring
Monitor Trends
Track scores over time to catch quality regressions early
API Reference
Key Endpoints
View full API documentation →
Related Features
Datasets
Create evaluation datasets from scored production traffic
Feedback
Combine automated scores with user feedback for comprehensive quality assessment
Experiments
Compare different configurations with consistent scoring
Custom Properties
Segment scores by feature, model, or experiment
Scores provide objective measurement of LLM response quality. Start with simple metrics like accuracy or helpfulness, then expand to framework-specific evaluations as your needs grow.
