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

# Crynux SDK

SDKs to bootstrap the application development

To speed up the integration of the Crynux Network into the applications. SDKs in several commonly used languages have been provided. The whole workflow to send the tasks and get the results are well encapsulated to be invoked easily.

### Crynux SDK in Python

The source code of the SDK in Python can be found on the GitHub:

{% embed url="<https://github.com/crynux-network/crynux-sdk-python>" %}

The example usages are provided in the README of the project.

### Crynux SDK in Go

The SDK in Go will be released shortly.

### Crynux SDK in JavaScript

The source code of the SDK in JavaScript can be found on the GitHub:

{% embed url="<https://github.com/crynux-network/crynux-sdk-js>" %}

The example usages are provided in the README of the project.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.crynux.io/application-development/crynux-sdk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
