Dashboard Guide
Navigate Usage, Errors, Fallbacks, and Alerts in your Revo Mail console.
Usage Overview
Access your usage dashboard at revomail.io → Usage.
Four top-level stats give you an instant snapshot:
- Total Requests — all API calls in the selected period
- Total Tokens — combined input + output tokens
- Total Spend — aggregate cost across all models
- Avg Tokens/Request — average token consumption per call
Highlights
Four visual cards sit at the top of the Usage page:
| Card | What It Shows |
|---|---|
| Top Spending | Model with the highest total cost, displayed as a percentage of your total spend |
| Most Requests | Model with the highest call volume, displayed as a percentage of total requests |
| Most Tokens | Model consuming the most tokens, displayed as a percentage of total tokens |
| Best Value | Model with the lowest cost per request (requires 3+ requests to qualify) |
Each card includes a donut chart for quick visual comparison against the rest of your usage.
Cost Over Time
A stacked bar chart shows daily spend broken down by model. Use the time-range selector to filter by 7, 30, or 90 days. Hover over any bar to see a per-model daily cost tooltip.
Cost by Model
Individual cards show each model's total cost and call count, sorted by spend (highest first). Use this section to quickly spot which models are consuming the largest share of your budget.
Cache Savings
This section appears once you have cache hits. It shows:
- Total savings from cache hits (dollar amount)
- Hit rate — cache hits as a percentage of total requests
- Hits vs. total requests — raw numbers for easy verification
See Advanced Features → Request Caching for details on how caching works.
Error Tracking
Access at revomail.io → Errors (sidebar).
Summary
Three cards at the top: total errors, error rate, and most common error type.
Error Trend
A 7-day chart shows how your error volume changes over time.
Recent Errors Table
Each row shows the error with a type badge. Error types you may see:
| Type | Meaning |
|---|---|
| Provider Outage | The upstream provider is down |
| Provider Timeout | The upstream provider didn't respond in time |
| Invalid Response | The upstream returned a malformed response |
| Model Unavailable | The requested model is offline |
Note: Internal errors (rate limits, balance issues) are not exposed — only provider-side issues are shown.
Fallback Configuration
- Go to Console → Key Management
- Click Fallback Rules on any API key
- Add model → fallback model mappings
- Enable or disable individual rules as needed
- Delete rules you no longer need
See Advanced Features → Fallback Chains for the full walkthrough.
Alert Configuration
- Go to Console → Account Settings → Alerts & Notifications
- Toggle each alert type on or off
- Set thresholds for Low Balance and Spend Limit
- Optionally add a webhook URL for custom integrations
- View the recent alerts table to track what's been triggered
See Advanced Features → Alerts & Notifications for details on each alert type.