> 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/tapai-with-authentication.md).

# TapAI with Authentication

{% hint style="warning" %}
Ixkio recommend using TapAI with authentication NFC tags only to protect usage. 
{% endhint %}

TapAI can be used with standard NFC tags and even QR Codes. However, ixkio strongly recommend using TapAI with authentication (NTAG424) NFC tags only. 

The TapAI feature uses credits which you pay for. The cost of this is very low and we are working on driving the pricing cheaper - but it still costs you money. 

When you use authentication NFC tags, you can configure your ixkio project so that the user must have scanned the NFC tag to access TapAI. 

If you use standard NFC tags or QR codes, then the static link could be shared anywhere on social media. Anyone with the link can then use TapAI. You could have thousands of people asking questions on your product - without access to it. 


---

# 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.ixkio.com/modules/tapai/tapai-with-authentication.md?ask=<question>&goal=<user_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.