> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/publish/adaptive-content.md).
# Adaptive content
Deliver a tailored documentation experience based on who's reading
When a user visits your site, you may already know things about them — such as who they are, which plan they’re subscribed to, and which features they have access to.
Adaptive content helps to build a tailored documentation experience based on who is reading.
Personalize your user’s documentation experience through adaptive content
{% hint style="info" %}
Adaptive content is slightly different from [authenticated access](/docs/publish/site-audience/authenticated-access.md), although they can work together.
While authenticated access allows you to protect your docs through a login, adaptive content customizes published material based on various authentication methods — including authenticated access or those from your own app.
{% endhint %}
### How it works
Adaptive content works in one of two ways:
1. Passing data from your app to GitBook
2. Passing data from authenticated access
When a user visits your sites, we call the data they bring with them their “claims” — basically data that helps to identify a user. These claims are controllable by you — the site author — and can be used through the GitBook editor to show or hide different pages, variants, and sections in your docs.
You can also use conditions to target human visitors or AI agents. See [targeting human visitors and AI agents](/docs/publish/adaptive-content/adapting-your-content.md#target-human-visitors-and-ai-agents).
Head to our page about [enabling adaptive content](/docs/publish/adaptive-content/enabling-adaptive-content.md) to start setting up adaptive content for your site.
---
# 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://gitbook.com/docs/publish/adaptive-content.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.
