> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/development-infrastructure/sdks-and-apis.md). # SDKs and APIs The SDKs and APIs section provides information about available tools and interfaces for interacting with the æternity blockchain. The JavaScript SDK is our primary and actively maintained development kit, offering comprehensive functionality for building applications on æternity. While there are other SDKs available (Python, Go, etc.), these are currently not actively maintained but may still offer useful reference implementations. In terms of APIs, the Node API serves as the core interface for blockchain interactions, with additional APIs to be documented as they are developed or discovered. This section aims to provide developers with the necessary resources to effectively build and integrate with the æternity ecosystem.
Javascript/Typescript SDKJavascript/Typescript SDKflip-30deg-gradient2.svg
Outdated SDKsOutdated SDKs30deg-gradient.svg
Node APIhttps://docs.aeternity.com/developer-documentation/protocol/node/apiflip-30deg-gradient.svg
Node API Swagger explorerhttps://api-docs.aeternity.io/15deg-gradient.svg
--- # 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.aeternity.com/aeternity-developer-tools/development-infrastructure/sdks-and-apis.md?ask=&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.