> For the complete documentation index, see [llms.txt](https://docs.testmace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testmace.com/master/project/nodes.md).

# Node Types

{% hint style="info" %}
A node is an element of the project or scratches tree.
{% endhint %}

### Node Types

* [**Project**](/master/node-types/project.md)**.** This is a root node, that is created automatically when you start a new project. It is functionally identical to a Folder node.
* [**Folder**](/master/node-types/folder.md)**.** It allows to group Folder and RequestStep nodes under it.
* [**RequestStep**](/master/node-types/request-step.md). This is a node that you can use to send a request. It can have only one Assertion node as a child element.
* [**Assertion**](/master/node-types/assertion-node.md). This one is used for writing tests. It can be a child node only for a RequestStep node.
* [**Script**](/master/node-types/script.md). It allows to run a JavaScript script and access the app's API.
* [**Link**](/master/node-types/link.md). Allows to access an existing node.
* [**Api description**](/master/node-types/api-description.md)
  * [**ApiRootFolder**](/master/node-types/api-description/apirootfolder.md)**.** A root element (folder) for API description.
  * [**ApiFolder**](/master/node-types/api-description/apifolder.md)**.** Groups logically close API description endpoints (e.g. two endpoints with the same urls but different methods).
  * [**ApiRoute**](/master/node-types/api-description/apiroute.md)**.** A specific endpoint description.
* [**Broken**](/master/node-types/broken.md)**.**  It is used for descripting nodes that were loaded unsuccessfully. Can't be created manually and is not stored in the file system.


---

# 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.testmace.com/master/project/nodes.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.