How to check Tarno's operational status live

Tarno exposes a read contract over the neutral INAPI corpus, kept fresh by three INAPI sources. Every operational signal — liveness, corpus freshness, and sync history — is queryable by you in real time through the endpoints below.

This page does not embed a live dashboard: the signals are exposed by the API, not by this page. Instead of showing values that would go stale, it teaches you which endpoints to call yourself to read the current status at any time.

Throughout this page the base URL is written as the environment variable TARNO_BASE_URL (= https://api.tarno.cl) and the key as TARNO_API_KEY. Replace the <API_KEY> placeholder with your real key at runtime; never commit it to version control.

export TARNO_BASE_URL="https://api.tarno.cl"
export TARNO_API_KEY="<API_KEY>"   # the opaque key string your operator issued

Liveness

GET /health is the public liveness probe — it is the only signal that requires no key. It returns 200 when the service is healthy and 503 when it is degraded.

curl -sS -o /dev/null -w "%{http_code}\n" "$TARNO_BASE_URL/health"

A 200 confirms the read contract is up; a 503 indicates the service is degraded.

Corpus freshness

Three INAPI sources keep the corpus fresh. Per-source freshness — how recent each source's data is against a staleness threshold — is reported live by GET /v1/freshness (scope insights:read):

curl -sS "$TARNO_BASE_URL/v1/freshness" -H "X-API-Key: $TARNO_API_KEY"

For the history of sync runs (when each pipeline ran and its outcome), call GET /v1/sync-runs (scope insights:read):

curl -sS "$TARNO_BASE_URL/v1/sync-runs" -H "X-API-Key: $TARNO_API_KEY"

The table below is only a reference for how often INAPI publishes each source — it is not a status value. The live truth about how fresh each source is right now comes from GET /v1/freshness, not from this table.

Source	INAPI publication cadence (reference)
Sheets	Daily
Estado-Diario	Monday–Friday (Santiago time)
Buscador	Continuous (scraped on the managed cron)

Read contract

These are Tarno's operational surfaces and how to verify each one yourself:

Surface	How to verify it
REST API (/v1)	Key-authenticated; verify with any GET /v1/... (e.g. GET /v1/freshness).
MCP server (Streamable HTTP)	Key-authenticated; REST-parity tools; see the MCP guide.
OpenAPI reference (https://api.tarno.cl/docs)	Public; open it in the browser to explore the interactive schema.
Liveness (/health)	Public; use the curl from the Liveness section.

Availability and expected freshness

The availability stance (single machine, best-effort) and the expected freshness cadence are documented in the SLA. Treat GET /v1/freshness, not this page, as the live truth about how fresh the corpus is right now.