Skip documentation navigation

Service health

Use the machine endpoints for service health, data freshness and provider evidence.

Read service health

Health checks describe whether the website, APIs, indexer and data providers can answer requests. They are separate from a launch record and from the evidence attached to a specific contract or wallet.

Use the response timestamp and block together.

A successful response can still contain data from an older block. Consumers should check freshness, provider agreement and finality before displaying time-sensitive values.

Machine sources

API health

Provider agreement, freshness, finality and route checks.

Open API health — opens website in a new tab

Deployment manifest

Chain, contract ranges, versions and immutable bindings.

Open deployment manifest — opens website in a new tab

What health checks prove

  • They describe the response and data sources at a point in time.
  • They do not approve a project or authorize a wallet transaction.
  • They do not prove safety, liquidity, price or token value.
  • They do not replace a finalized onchain receipt.