> For the complete documentation index, see [llms.txt](https://developers.verida.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.verida.network/protocol/client-sdk/configuration.md).

# Configuration

## Client configuration[​](https://developers.verida.network/docs/client-sdk/configuration#client-configuration) <a href="#client-configuration" id="client-configuration"></a>

An options parameter can be passed to the `Client` object:

```typescript
import { ClientConfig, Network } from '@verida/types'

const config: ClientConfig = {
  network: Network.BANKSIA,
  didClientConfig: {
    rpcUrl: "https://<your-custom-polygon-url>"
  }
}

const client = new Client(config)
```

Some key options are:

* `network` — Sets default configuration settings for the specified environment. Options are; `local`, `banksia`, `myrtle`
* `didClientConfig.rpcUrl` - While optional you may want to set your own RPC instead of using the default RPC of the Client (free and public but may not be reliable)

## Environment Variables[​](https://developers.verida.network/docs/client-sdk/configuration#environment-variables) <a href="#environment-variables" id="environment-variables"></a>

As you deploy your application on different environments (Production, test, staging), you may want to set a `VERIDA_NETWORK` and `POLYGON_RPC_URL` environment variable in your application to choose the network and RPC to use appropriately. Note that the client does not read the environment variables and so there is no syntax imposed on the naming of the variables. It is up to you to pass the environment variable to the `ClientConfig`.

For example:

```bash
VERIDA_NETWORK=banksia
POLYGON_RPC_URL=https://<your-custom-polygon-url>
```

{% hint style="info" %}
&#x20;Refer to the documentation of your framework, if any, for how to set and use encironment variables.
{% endhint %}


---

# 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://developers.verida.network/protocol/client-sdk/configuration.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.