> 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/javascript-typescript-sdk.md).
# Javascript/Typescript SDK
The æternity JavaScript SDK is a comprehensive toolkit that enables developers to interact with the æternity blockchain using JavaScript. Whether you're building decentralized applications (æpps), integrating blockchain functionality into existing applications, or developing tools for the æternity ecosystem, this SDK provides all the necessary methods and utilities to work with æternity's features, including smart contracts, oracles, naming system (AENS), and state channels.
This documentation covers everything from basic setup to advanced blockchain interactions. You'll find detailed guides for core functionalities, examples for common use cases, and comprehensive API references. The documentation is structured to support both newcomers getting started with blockchain development and experienced developers looking to leverage æternity's full feature set. Navigate through the sections on the left to find detailed information about specific features and functionalities.
---
# 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/javascript-typescript-sdk.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.
