> For the complete documentation index, see [llms.txt](https://docs.taal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taal.com/core-products/1sat-ordinals-tokens-api/basic-tutorial-node.md).

# Basic Tutorial - Node

**Github Repository**

[**https://github.com/TAAL-GmbH/1sat-tutorial**](https://github.com/TAAL-GmbH/1sat-tutorial)

`mkdir 1sat-tutorial`

cd `1sat-tutorial`

Demo code using our 1Sat Token Studio API can be found on Github so you can clone our repository or if you want to do it manually, we need to make now a node project

`npm init`

and answer in the questions.

Let’s add the dependencies\
`npm install bsv@1.5.4` \
`npm install axios`

Make sure your package.json looks like this (you might need to change the type to “module” and add a new entry to run the tutorial- `"tutorial": "node index.js"`\ <br>

`{ "name": "1sat-tutorial",` \
&#x20;  `"version": "1.0.0",` \
&#x20;  `"description": "1sat-tutorial",` \
&#x20;  `"type": "module",` \
&#x20;  `"main": "index.js",` \
&#x20;  `"scripts": { "test": "echo \"Error: no test specified\" && exit 1",` \
&#x20;               `"tutorial": "node index.js"` \
&#x20;   `},`\
&#x20;  `"author": "TAAL",`\
&#x20;  `"license": "ISC",` \
&#x20;  `"dependencies": {` \
&#x20;        `"dependencies": { "axios": "^1.7.2",` \
&#x20;                          `"bsv": "^1.5.4"`  \
&#x20;   `}` \
`}`

Now we are ready to start coding. Create the main file you specified during the setup e.g. `index.js`in the root of the `1sat-tutorial` folder as well as the helping file 1sat\_utils.cjs using your editor or IDE of choice.

1. Copy the code from our files and paste.
2. in index.js you will need to replace the sample API key from your TAAL API Key
3. You can also tune which steps to run, only the creation of a single/standalone token, the inscription of a collection with one item or individual steps you may want to debug in depth e.g.\ <br>

   `const STEPS_TO_TEST =[ 'single', 'collection'];` \
   `///const STEPS_TO_TEST =['1.1','1.2','1.3','1.4','1.5', '1.6', '1.7']; //const STEPS_TO_TEST =['2.1','2.2','2.3','2.4','2.5', '2.6', '2.7', '2.8', '2.9'];`

&#x20;

You can test now. If all was properly configured you should see something like this:

&#x20;

<figure><img src="/files/3jyHZOoUOfsBKIa5cIJA" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/sDgd5N3pquBW4wBDiNfW" alt="" width="375"><figcaption></figcaption></figure>

&#x20;

Add label


---

# 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.taal.com/core-products/1sat-ordinals-tokens-api/basic-tutorial-node.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.
