> 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/getting-started/organisation-structure/tags/using-authentication-ntag424-nfc-tags.md).

# Using Authentication (NTAG424) NFC Tags

## Authentication Tags and Keys

Ixkio will store the keys used for tag authentication. For security reasons, tag keys are not visible via the console. You can access the keys at any time by contacting us and we set up a one time download option. 

#### Authentication (NTAG424) NFC Tags purchased from Seritag

During the encoding process, Seritag will upload the tag encryption keys to ixkio so that your tags are ready to use. They are *your* Tag Authentication Keys and you can request them at any time by contacting us. 

#### Authentication (NTAG424) NFC Tags encoded with the ixkio mobile app

If you are encoding blank NTAG424 tags with the ixkio mobile app, then ixkio will automatically generate the keys and store them. As always, they are *your* Tag Authentication Keys and you can request them at any time.

#### Authentication Tags encoded using other platforms

You can upload NTAG424 keys to the ixkio platform at the batch level. This setting is not enabled by default - contact us to add this function to your account. 

The NTAG424 tag can be encoded in a large number of different permutations. Ixkio supports four different encoding settings and it's important that tags are encoded in a certain way so they work correctly. Contact us for more information. 


---

# 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/getting-started/organisation-structure/tags/using-authentication-ntag424-nfc-tags.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.