> Parel documentation. Index of every page: https://parel.si/docs/llms.txt. This page in HTML: https://parel.si/docs/support

# Status and support

> Where Parel runs, how to tell whether something is down, and how to reach a person.

## Where things run

| Service | Address |
|---|---|
| API and MCP endpoint | `https://api.parel.si` (`/v1/*`, `/mcp`) |
| Dashboard | [app.parel.si](https://app.parel.si) |
| This site and the docs | parel.si |

Parel is in a closed beta. There is no automated status page yet; the [status page](https://parel.si/status) says what runs where and will point at an uptime history when one exists. Planned maintenance is announced there before it starts.

## Is it down, or is it me

- `GET https://api.parel.si/health` answers 200 with `ok: true` when the database is reachable; it reports `degraded: true` (still 200) when the exchange rate is stale or the source does not answer, and 503 only when the database is down.
- An `upstream_*` error on a call means the source, not Parel, did not answer; it is ₹0 and usually retryable. `paused` (503) means Parel has paused all calls for an incident or maintenance; nothing is charged while paused.
- A 401 means the credential, not the service. [Authentication](https://parel.si/docs/api/authentication.md).

## Reaching us

Email [hello@parel.si](mailto:hello@parel.si). Include the `request_id` (the `X-Request-Id` header, in every error body) and, for a call, the `call_id`. Failed calls are never charged, so a retry a few minutes later costs nothing.

- A charged result that was useless: **Report bad result** on the call in the dashboard's usage log within 7 days; small amounts come back at once. [Refund Policy](https://parel.si/legal/refunds).
- More credit during the beta: the team name, to the same address.
- Security reports: the same address; see [Security](https://parel.si/legal/security).
- Grievances under the DPDP Act: acknowledged within 48 hours, resolved within 30 days. [Privacy Notice](https://parel.si/legal/privacy).
