> For the complete documentation index, see [llms.txt](https://exliquid.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://exliquid.gitbook.io/docs/developers/sdk.md).

# SDKs

Exliquid maintains TypeScript and Python SDKs for client integration.

The SDKs exist to make transaction construction, signing, REST queries and WebSocket consumption easier and safer. They do not replace the versioned network/API contract.

## TypeScript SDK

The TypeScript package is named:

```
@exliquid/sdk
```

It is intended for:

* browser and User App integrations;
* Node.js trading services;
* TypeScript bots and tooling;
* typed REST and transaction workflows.

The current source package is versioned independently from the network. Use only the SDK version listed as supported in [Networks and versions](/docs/reference/networks-and-versions.md) for a public network.

## Python SDK

The Python SDK is intended for:

* execution and market-making bots;
* quantitative and research tools;
* automated integration tests;
* service-side trading integrations.

The maintained examples cover flows such as:

* owner-signed order submission;
* agent authorization and trading;
* Faucet request and transaction confirmation;
* WebSocket market subscription;
* paginated authorization queries.

## What a supported SDK should handle

A client SDK should help with:

* network and protocol identity;
* numeric and identifier validation;
* typed transaction construction;
* EIP-712 signing data;
* signed transaction serialization;
* REST requests and typed responses;
* idempotent transaction submission;
* transaction confirmation;
* WebSocket subscriptions and sequence handling;
* structured API errors.

## Signing responsibility

The SDK can construct the typed message, but the wallet or signing agent remains responsible for authorizing it.

Applications should display meaningful action details before requesting a signature.

## Compatibility

SDK and network compatibility is explicit. Before submitting a signed action, verify that the SDK supports the network/API/protocol identifiers published for the target environment.

During the current pre-release stage, older development networks should not be assumed to remain compatible with the latest SDK.

## Installation

Copy-paste installation commands are published together with the supported public SDK release. Until then, do not infer package availability from source-directory names alone.

See [Integration quickstart](/docs/developers/integration-quickstart.md) and [Transactions and signing](/docs/developers/transactions-and-signing.md).


---

# 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://exliquid.gitbook.io/docs/developers/sdk.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.