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

# SDKs

> Choose a client — TypeScript, Python, or raw HTTP — and when to use each.

The Alterscope API is plain HTTPS + JSON, so any HTTP client can call it. First-party SDKs add typed models, the agentic-envelope helpers, retry, and pagination so you write less boilerplate.

| Client                                 | Package             | Status | Use when                                                      |
| -------------------------------------- | ------------------- | ------ | ------------------------------------------------------------- |
| [TypeScript](/develop/sdks/typescript) | `@alterscope/sdk`   | Beta   | Node 20+ or browser apps. Typed resources + envelope helpers. |
| [Python](/develop/sdks/python)         | `alterscope` (PyPI) | Beta   | Sync or async Python; data/quant workflows.                   |
| [curl / raw HTTP](/develop/sdks/curl)  | —                   | Always | Shell scripts, quick checks, or any language without an SDK.  |

## Install

```bash theme={null}
# TypeScript
npm install @alterscope/sdk

# Python
pip install alterscope
# with async support
pip install "alterscope[async]"
```

## SDK or raw HTTP?

* **Use an SDK** when you want typed responses, automatic retries, pagination helpers, and the `freshnessStatusOf` / `freshness_status_of` envelope helpers without writing them yourself.
* **Use raw HTTP** for one-off calls, shell scripts, languages without a first-party SDK, or when you want full control over the wire. See [curl](/develop/sdks/curl).

Whichever you choose, authentication and the response envelope are identical — see [Authentication](/develop/get-started/authentication) and [Response envelope](/develop/concepts/response-envelope).