---
title: "Pipeline health"
method: GET
path: "/v1/ops/pipeline-health"
---

# Pipeline health

`GET /v1/ops/pipeline-health`

## Request

- Base URL: `https://api.onvexia.com`
- URL: `https://api.onvexia.com/v1/ops/pipeline-health`
- Auth: one of:
  - API key in header `X-API-Key`
  - API key in header `Authorization`
  - API key in header `X-PAYMENT`

Reports which tier cannot finish inside its own interval. WHY SATURATION IS THE HEADLINE AND NOT A LIST OF GREEN TICKS. Measured 2026-08-28: all nine hourly steps were SUCCEEDING, and the hourly tier was at 178.2% (6,416s of average work against a 3,600s interval). A status board would have been entirely green while the shared pipeline lock was held continuously. "Everything passed" and "the tier is keeping up" are different claims.

## Response `200`

OK

## Other responses

- `402`: Payment required (x402): no account needed, pay per call
- `404`: Not found, or metric registered but not yet served (the body names it)

---

[API](https://skmtc.dev/onvexia/apis/onvexia-crypto-sentiment-whale-tracking-onchain-analytics-ap.md) · [All operations](https://skmtc.dev/onvexia/apis/onvexia-crypto-sentiment-whale-tracking-onchain-analytics-ap/llms.txt) · [OpenAPI document](https://skmtc.dev/onvexia/apis/onvexia-crypto-sentiment-whale-tracking-onchain-analytics-ap/revisions/7619665fc084?raw)