Monitoring
Health Scores
Understand the 0–100 stability rating for every API.
Every API you monitor gets a health score — a 0–100 rating that reflects its stability over time.
How scores are calculated
Health scores are based on:
- Change frequency — APIs that change constantly score lower
- Severity distribution — breaking changes weigh heavily, cosmetic changes don't
- Recency — recent changes matter more than old ones
- Consistency — erratic update patterns score lower than predictable ones
Scores are updated daily after each scan cycle.
Reading the score
| Score | Rating | What it means |
|---|---|---|
| 80–100 | Stable | Few changes, mostly non-breaking. Safe to depend on. |
| 60–79 | Moderate | Regular changes but mostly manageable. Stay alert. |
| Below 60 | Volatile | Frequent or breaking changes. High maintenance risk. |
Using scores
Health scores help you:
- Prioritize monitoring — focus attention on volatile APIs
- Assess risk — before adopting a new API dependency, check its health score
- Spot trends — a declining score may signal an upcoming major version or deprecation cycle
Dashboard view
The dashboard shows health scores in two places:
- Stat cards — the average health score across all your monitored APIs
- API Health panel — individual scores for each API with a status indicator