> 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

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 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://docs.crynux.io/application-development/crynux-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.