> For the complete documentation index, see [llms.txt](https://manual.personr.co/api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.personr.co/api-documentation/pages/overview.md).
# Overview
Pages — an easier way to onboard clients.
Pages are customisable static verification pages that applicants or entities can access from a link that never changes, and one that you choose.
Instead of manually creating applicants or entities using the [Creating an applicant](/api-documentation/applicants/creating-an-applicant.md) or [Creating an entity](/api-documentation/entities/creating-an-entity.md) endpoints, Pages automatically creates the applicant or entity, displays your chosen verification flow for the client to go through, and the results are magically made available in your dashboard.
During setup, you can:
* Customise the page title, and favicon displayed in the browser;
* Choose your domain, and the URL path of your link;
* Select which flow to verify clients on;
* Adjust the colours, and logo, to suit your brand;
* Include your privacy policy link, or use ours; and
* Add custom code, like Google Analytics, to the HTML header of the page.
Once an applicant or entity has been verified using Pages, webhooks are sent and results can be retrieved as normal. Clients that have been automatically created with Pages are distinguished in your dashboard with the Pages symbol.
---
# 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://manual.personr.co/api-documentation/pages/overview.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.
.png?alt=media&token=81d59826-d7fd-4071-b86a-f79b8504ddfd)
