> For the complete documentation index, see [llms.txt](https://docs.ixkio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixkio.com/modules/tapai/adding-tapai-reference-material.md).

# Adding TapAI Reference Material

TapAI allows you to add freeform text information at the Active Folder, Tag Group and Batch levels. However, the system is designed so that the majority of information entered should be at the Active Folder level.  

| Level         | Allowed Text            |
| ------------- | ----------------------- |
| Active Folder | Up to 25,000 characters |
| Tag Group     | Up to 500 characters    |
| Batch         | Up to 500 characters    |

## Character Allowance

You can add up to 500 characters at the Tag Group and Batch level without any additional Credit charges. 

At the Active Folder level, you can include up to 2,500 characters to classify in the 'Small' Credit Usage band, up to 10,000 characters for the 'Medium' band and 25,000 characters in the 'Large' Credit band. 

As you increase the character count, the notification bar will indicate your usage. 

<div data-with-frame="true"><figure><img src="/files/nJh1UwPOFO0zIzMW46Vn" alt="" width="219"><figcaption></figcaption></figure></div>

The character allowance is based on the Active Folder only. The Tag Group and Batch characters do not count. Extended Data information also does not count.&#x20;

## Formatting your TapAI Text

Getting your TapAI text correct is vital for a good TapAI experience. AI systems generally recognise context better than pure facts but we recommend using both. For example :&#x20;

<div data-with-frame="true"><figure><img src="/files/tMhIj6fHXWgFh0KkkE6d" alt="" width="215"><figcaption></figcaption></figure></div>

Information here is written in both note form and in a written description. The combination of the two strengthens the data set.&#x20;

TapAI can only ever use information provided to give answers. It should not use wider internet information. However, it can connect information. For example :&#x20;

<div data-with-frame="true"><figure><img src="/files/GXuwlVbkY80Yv0cfjWao" alt="" width="218"><figcaption></figcaption></figure></div>

In this instance, if TapAI is asked by the user when the gurantee will ***expire,*** then it can use the two parts of information provided and respond 12th August 2027.&#x20;

## Folder, Tag Group and Batch Information

Ixkio is designed as a hierarchy system so that Tags inherit data from the tree they are in. In the same way, we would recommend entering information at each level so that it would match. For example, let's assume an electronics company selling a bluetooth speaker :&#x20;

| Level         | Example Information                                                                                                                                                                          |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Active Folder | Useful customer information such as support email, phone numbers or opening hours. Possibly company info such as when it was founded, how many staff or similar.                             |
| Tag Group     | Information about the products in general - how to connect the product with bluetooth, how to charge it or what batteries it needs. Whether it's waterproof or compatible with Android, etc. |
| Batch         | This might be more specific to a particular product batch. So information about model number or specific battery life.                                                                       |

## Extended Data

In addition to the freeform text fields, you can also select to include Extended Data. For example, you might have an Extended Data field (or Tag Name) to store product serial numbers, product colours, materials or similar.&#x20;

At the Active Folder level, you can select with Extended Data fields you want to include in your TapAI Information set.&#x20;

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

These will then dynamically be included and be available in TapAI. A user might therefore ask, 'What is the Serial Number' and get the specific Tag information in response.&#x20;

## Subtags

Users that are familier with using [Subtags](/features/subtags.md) can also include these in the freeform text fields. For example, you might include :&#x20;

<div data-with-frame="true"><figure><img src="/files/AquL16vkH98o3GUvJmms" alt="" width="563"><figcaption></figcaption></figure></div>

This will dynamically substitute information from Extended Data into the information set.&#x20;

In this example, the {dtcreated} subtag will dynamically add the date the Tag was created. A user asking which batch this Tag is part of, will see a response including the name of the Batch that that Tag is in within your ixkio project.&#x20;


---

# 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.ixkio.com/modules/tapai/adding-tapai-reference-material.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.