> 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/response-modes-explained.md).
# Response Modes Explained
## What is a Response Mode ?
Ixkio has three Response modes : Redirect, Direct and API.
With the Redirect response mode (often called dynamic links), users scanning your tag are redirected to another page - usually your website. With Direct Response mode, users scanning your tag will see a page created by ixkio.
You can create advanced rules (if you want) to allow some users to be redirected and some to see direct response pages.
All our plans offer both Redirect and Direct Response.
The Response Mode is set at the Active Folder level - you can choose from Redirect (all tags in that folder will be Redirect), Direct Response (all tags will have a page displayed by ixkio) or Dynamic (all tags can be configured with rules so tags can do either).
{% hint style="info" %}
The reason for the choice is simply to make the interface simpler by only showing options you need.
If you aren't sure what you might need - choose Dynamic !
{% endhint %}
## Redirect
The Redirect system allows management of what's typically called 'dynamic links' - ie, links whose destination can be quickly altered.
When the NFC tag is scanned, the user is directed to the ixkio platform. Ixkio checks where the tag needs to redirected to and redirects the user immediately. This happens almost instantly and user isn't aware of the redirect.
Setting up a redirect is quick, easy and flexible. It allows the management of tag destinations after the tags have been deployed.
## Direct Response
With Direct Response mode, ixkio displays the landing page directly on tag scan. No other website or server is required.
* Build templates using a drag and drop creator
* Upload your brand and content images
* Display data unique to each tag using [subtags](/features/subtags.md)
Direct Response
---
# 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/response-modes-explained.md?ask=&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.
## Direct Response
With Direct Response mode, ixkio displays the landing page directly on tag scan. No other website or server is required.
* Build templates using a drag and drop creator
* Upload your brand and content images
* Display data unique to each tag using [subtags](/features/subtags.md)