# Runtime status

Inspect the current DataNavoAPI build, catalog and local configuration. External providers are not probed; real payments are not connected.

## Current snapshot

The HTML page reads a snapshot when requested. Its refresh button reads public JSON again. This Markdown explains the source; it does not store a current operating state. The JSON endpoint never calls providers or exposes customer records.

[Read current public status](https://datanavoapi.com/api/public-status)

## A configuration snapshot

Read the current build, capability catalog and two live-mode flags. Refresh reads these values again without executing data APIs.

## No availability probes

External provider accounts, balances and quotas are not tested. This page does not publish invented uptime, latency or incident history.

## Business data stays private

This page does not read accounts, keys, orders, usage, database size or email content. Those records stay in the protected workspace.

## Interpreting the modes

Anonymous demos use fixed fictional fixtures. Customer gateway execution is simulated. Supplier and playground live flags are independent configuration values; either enabled flag causes an attention state, never a claim of provider availability. Real payments are not connected and external email is not sent.

## External providers

TikHub, ScrapeCreators and TwitterAPI.io are not checked. Unchecked does not mean healthy or failed. No uptime, latency or incident history is inferred.
