> For the complete documentation index, see [llms.txt](https://docs.whereby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whereby.com/reference/core-sdk-reference/api-reference/wherebyclient.md).

# WherebyClient

```jsx
import { WherebyClient } from "@whereby.com/core";

const client = new WherebyClient();
```

The WherebyClient is the main entry point for the Core SDK. It acts as a wrapper around the underlying state store and service layer, and gives you access to the specialized client classes.

Creating a WherebyClient automatically sets up the internal store and services. From there, you can retrieve the specific clients you need:

* LocalMediaClient → manage camera and microphone
* RoomConnectionClient → join/leave rooms, subscribe to remote participants, any in room actions

### Methods

| Method                | Returns                | Description                                                                                                            |
| --------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `new WherebyClient()` | `WherebyClient`        | Creates a new client instance with it’s own store and sub-clients. Construct once per session.                         |
| `getLocalMedia()`     | `LocalMediaClient`     | Manages local media streams. Use to start/stop local media and toggle tracks.                                          |
| `getRoomConnection()` | `RoomConnectionClient` | Manages and observes the room connection lifecycle. Use to initialize, join room and subscribe to remote participants. |
| `destroy()`           | `void`                 | Destroy all sub-clients and release resources. Always ccll at teardown to unsubscribe and clean up.                    |


---

# 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.whereby.com/reference/core-sdk-reference/api-reference/wherebyclient.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.