> Index: https://quebragalho.dev/en/docs/llms.txt

# Status

`GET /v1/status`

Each model's health over the last 24 hours, as JSON, for alerts, dashboards and automation.

## Two routes, the same data

**cURL**

```bash
curl "https://api.quebragalho.dev/v1/status?model=hy4-flash&model=muse-ember&incidents=7d" \
  -H "Authorization: Bearer $QUEBRAGALHO_API_KEY"

curl https://app.quebragalho.dev/api/public/status
```

- `GET /v1/status`: With your API key. Each model gets an `allowed` field: whether this key and your plan can use the model. It counts toward the limit of 60 reads per minute per key.
- `GET app.quebragalho.dev/api/public/status`: No key, served by the dashboard. The same JSON, without `allowed`. 15 s public cache and open CORS.

## Filter and request incidents

- `model`: Repeatable, up to 100. Returns only those models; `overall` still reflects the whole catalog.
- `incidents=7d`: Adds `incidents_7d`: degradations and outages over the last 7 days.
- `Accept-Language: en`: Notice titles and bodies in English instead of Portuguese, when a translation exists.

## What each state means

- `status`: `operational`, `degraded`, `outage`, `maintenance` or `no_data`. `no_data` is gray: not enough data to say it is fine.
- `overall`: `operational`, `partial` or `outage`. It only turns `outage` when half or more of the models with data are down, or when the whole platform fails.
- `stale`: `true` when the monitor has not updated for more than 3 min. Treat it as "unknown", not as an outage.

Only real customer traffic counts, with no synthetic tests. The full field reference is at [/status/api](https://app.quebragalho.dev/status/api).

Read it in the browser: https://quebragalho.dev/en/docs/api/status
