# l4 status

> Show LevelFour API health and the evaluation status of your account.

Source: https://docs.levelfour.ai/cli/commands/status


`l4 status` reports the API's health and your account's current evaluation state. Run it as a pre-flight check before heavier commands, or as a CI smoke test.

```bash
l4 status
```

> **Success**
>
> A plain run prints a `Status` line and a `Base URL` line. Those two lines are the proof the API answered, and the base URL confirms which API you reached.

Global flags (`--json`, `--jq`, `--template`, `--quiet`, `--token`, `--api`) apply. See [CLI overview](/cli#global-flags). Exit codes follow the [standard CLI exit conventions](/cli#exit-codes).

> **Note**
>
> `l4 status` resolves a credential before it calls anything, so a CI runner with no `LEVELFOUR_TOKEN` set fails on authentication rather than reporting on the API. [CLI authentication](/cli/authentication) has the resolution order and the troubleshooting table.

## Examples

Pipe to JSON for monitoring scripts:

```bash
l4 status --json
```

Reduce the run to an exit code, with nothing on stdout or stderr:

```bash
l4 status --quiet
```

[Output formats](/cli/output-formats#--quiet) has what `--quiet` suppresses and how to read the result from `$?`.

## Related

* [`l4 whoami`](/cli/authentication#inspect-the-active-session): identity and organization context
* [`l4 mcp status`](/cli/commands/mcp/status): a different status (which agent clients carry a LevelFour entry)
