> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reducto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Checking API Health & Usage

> Check Reducto hosted API availability, usage, and throttling signals

Use this page to check the availability of the Reducto API and monitor your usage and throttling signals.

## Check hosted API availability

If you use the hosted Reducto API at `platform.reducto.ai`, check [status.reducto.ai](https://status.reducto.ai) for uptime and incident information. Subscribe to status updates there to receive notifications about incidents and maintenance.

For a lightweight connectivity check, request `GET /version`. It returns the current API version string:

```bash theme={null}
curl "https://platform.reducto.ai/version" \
  -H "Authorization: Bearer $REDUCTO_API_KEY"
```

To also verify that your API key is valid, request `GET /jobs?limit=1`:

```bash theme={null}
curl "https://platform.reducto.ai/jobs?limit=1" \
  -H "Authorization: Bearer $REDUCTO_API_KEY"
```

A `200` response confirms the API is reachable and your key is valid. A `401` indicates an invalid or expired API key. A `403` with an HTML error page means the request was sent without an `Authorization` header. For transient failures, retry according to your client's retry policy.

## Self-hosted and on-premise deployments

If you run Reducto in your own environment, reach out to the Reducto team at [support@reducto.ai](mailto:support@reducto.ai) for monitoring and observability guidance specific to your deployment.

## Check usage and throttling

* Use the [Usage Export API](/reference/usage-export-api) for programmatic usage and credit data.
* Use [Rate Limits](/reference/rate-limits) to identify request-rate `429` responses.
* Use [Concurrency Throttle](/reference/throttling) to understand queued work and latency caused by account-level concurrency limits.