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

# Choose an Integration Path

There are three normal ways to use the Developer SDK.

## 1. Server SDK

Use the server SDK when you want full control over your backend route shape,
auth checks, request validation, and response format.

Main entrypoint:

<CodeGroup dropdown>
  ```typescript TypeScript theme={null}
  import { SwigClient } from '@swig-wallet/developer-sdk/server/typescript';
  ```

  ```python Python theme={null}
  from swig_developer_sdk import SwigClient
  ```
</CodeGroup>

## 2. Proxy helpers

Use the framework helpers when you want the API key to stay on the server and
the SDK to implement the prepare routes.

Main entrypoints:

<CodeGroup dropdown>
  ```typescript TypeScript theme={null}
  import { createSwigRouteHandlers } from '@swig-wallet/developer-sdk/next';
  import { createSwigNestHandler } from '@swig-wallet/developer-sdk/nest';
  ```

  ```python Python theme={null}
  from swig_developer_sdk import SwigProxyConfig, create_swig_proxy_handler

  handler = create_swig_proxy_handler(SwigProxyConfig())
  ```
</CodeGroup>

## 3. Browser client against your own proxy

Use the browser client when your frontend should work with wallet handles and
prepared results, while still calling only your own app routes.

<Note>
  The browser client is TypeScript-only. Python provides the equivalent
  server-side proxy handler, while browser signing remains in your frontend.
</Note>

Main entrypoint:

```typescript theme={null}
import { SwigBrowserClient } from '@swig-wallet/developer-sdk/browser';
```

## Practical rule

* choose the server SDK if you want maximum control
* choose the framework helpers if you want the fastest route-based setup
* choose the browser client only together with one of the server-side options