---
title: "Index freshness and depth"
method: GET
path: "/arc/status"
tags: ["Arc data"]
---

# Index freshness and depth

`GET /arc/status`

## Request

- Base URL: `https://api.getchord.xyz/v1`
- URL: `https://api.getchord.xyz/v1/arc/status`
- Auth: none declared

Is the Arc rollup fresh, how far back it reaches, and the state of the pool index and the holder ledger. Check this before trusting a quiet number.

Served from Chord's rollup and index tables (every swap on Arc summed by hour, token and venue), never from a raw scan — so calls are cheap and every answer carries its coverage. No key needed. `503 NOT_READY` until the rollup has run on the deployment.

## Response `200`

- object
  - `chain` 5042
  - `enabled` boolean
  - `recentAt` integer, nullable: Unix time, seconds, UTC.
  - `staleSec` integer, nullable
  - `floorHour` integer, nullable
  - `genesisHour` integer, nullable
  - `backfillComplete` boolean
  - `index` object, nullable
    - `pools` integer: V2 + V3 pools indexed.
    - `v4Pools` integer
    - `cursor` integer: Last block the pool crawler processed.
    - `genesis` boolean: Pool discovery reached genesis.
  - `holders` object, nullable: Holder-ledger lane state (tracked tokens, completed backfills, cursors).
  - `updatedAt` integer: Unix time, milliseconds — when the server built this answer.

## Other responses

- `503`: The lane behind this endpoint is not ready or not enabled here (`NOT_READY`, `CHAIN_NOT_ENABLED`, `NOT_ENABLED`, `*_UNAVAILABLE`). Retry later; do not treat it as an empty answer.

---

[API](https://skmtc.dev/getchord/apis/chord-api.md) · [All operations](https://skmtc.dev/getchord/apis/chord-api/llms.txt) · [OpenAPI document](https://skmtc.dev/getchord/apis/chord-api/revisions/d3bc4640fea0?raw)