Status
This page reports the operational status of the IRIS read contract and of the three INAPI ingestion pipelines that keep the corpus fresh.
This is a static snapshot, not a live dashboard yet. Live status will be wired post-box-deploy from the
GET /v1/freshnessendpoint (scopeinsights:read) plus the Phase-4 observability surface. The per-source rows below describe the intended sources and their cadence — they are not real-time readings. Do not treat the indicators here as a live health signal until the live wiring lands (see Live wiring below).
Read contract
| Surface | Status | Notes |
|---|---|---|
REST API (/v1) |
Operational | Versioned read contract; API-key authenticated. |
| MCP server | Operational | Streamable HTTP; API-key authenticated; REST-parity tools. |
OpenAPI reference (/docs) |
Operational | Live Scalar reference, public. |
Liveness (/health) |
Operational | Public probe (200 ok / 503 degraded). |
Ingestion pipelines (corpus freshness)
Three INAPI sources feed the corpus. Their freshness is what GET /v1/freshness reports
per-source once live wiring lands.
| Source | Publication cadence (INAPI) | Status |
|---|---|---|
| Sheets | Daily | Snapshot |
| Estado-Diario | Monday–Friday (Santiago time) | Snapshot |
| Buscador | Continuous (scraped on the managed cron) | Snapshot |
The expected freshness cadence and the honest uptime stance are documented in the SLA. "Snapshot" means the value above is a static placeholder, not a live reading.
Live wiring (deferred — operator / box step)
Wiring this page to live data is a deferred operator step that depends on the box deploy and the observability surface landing. It is out of scope for the documentation and is not built here. Once the box deploy lands, the operator replaces the static snapshot above with live data sourced from:
GET /v1/freshness(scopeinsights:read) — per-source staleness for Sheets, Estado-Diario, and Buscador, against a configurable staleness threshold.- The Phase-4 observability surface — service health, sync-run history, and per-route / per-consumer metrics.
Until then, an integrator who needs a current freshness reading should call
GET /v1/freshness directly with an insights:read key.