> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/cli/ready.md).

# sdm ready

```shell
NAME:
   sdm ready - reports if the listener is ready for use.

USAGE:
   sdm ready [command options] [datasource name]

DESCRIPTION:
   sdm ready reports if the listener is ready for use.

        This command returns a detailed view on whether the StrongDM client is
    ready to serve connections. It uses the binary combination of the following
    codes to indicate what could be wrong:

        255    indicates that some internal error has happened and it cannot assert readiness.
          1    the StrongDM listener is not running.
          2    the StrongDM listener did not load its internal state yet or the user is not logged in.
          4    the StrongDM listener is not yet connected to a gateway.
          8    datasource name does not match any of the known datasources for the logged in account.
         16    there is not a gateway with a possible route to the chosen datasource.
         32    the chosen datasource is not connected.


OPTIONS:
   --quiet, -q  do not print the details in the standard error
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.strongdm.com/references/cli/ready.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.