> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alshival.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# SDK overview

> Install, configure, and choose the right integration path

Use SDKs when you want log-level filtering, structured payload generation, and MCP tool helpers out of the box.

## Install

<Tabs>
  <Tab title="Python">
    ```bash theme={null}
    pip install git+https://github.com/Alshival-Ai/alshival.git@main
    ```
  </Tab>

  <Tab title="Node.js">
    ```bash theme={null}
    npm install @alshival.ai/alshival
    ```
  </Tab>
</Tabs>

## Shared environment variables

```env theme={null}
ALSHIVAL_USERNAME=your_username
ALSHIVAL_API_KEY=your_api_key
ALSHIVAL_RESOURCE=https://alshival.dev/u/resource_owner_username/resources/resource_uuid/
ALSHIVAL_CLOUD_LEVEL=INFO
ALSHIVAL_DEBUG=false
```

Copy `ALSHIVAL_RESOURCE` from the DevTools Resource Details page's **Resource URL** field. This works for both owned and shared resources.

## Cloud forwarding levels

Accepted values:

* `DEBUG`
* `INFO`
* `WARNING`
* `ERROR`
* `ALERT`
* `NONE` (disable cloud forwarding)

Values are case-insensitive.

## Which page next

* `/sdk/python` for Python-specific API examples
* `/sdk/nodejs` for Node.js-specific API examples
* `/sdk/curl` for direct HTTP integrations without SDKs