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

# The DeSo Python SDK

Everything you need to construct, sign, and submit transactions is in [the DeSo Python SDK](https://github.com/deso-protocol/deso-python-sdk). This is an advanced library that makes it extremely easy to do all of DeSo’s basic (and not-so-basic) transaction types.

The best way to learn is to simply go through the README and run the code. Once you’ve gotten everything to a “SUCCESS” status, you can proceed to the challenges, which simultaneously walk you through how to build an advanced market-making bot, as well as advanced social bots.

Read the next sections to learn how to get help from the community and test your knowledge.


---

# 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.deso.org/openfund/the-deso-python-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.
