> For the complete documentation index, see [llms.txt](https://detected.gitbook.io/detected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://detected.gitbook.io/detected-docs/api-overview/terminology.md).

# Terminology

|                   |                                                                                                                                                                             |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Profile           | The core 'case' within Detected, a profile holds all the information on the entity, the representatives and all associated compliance information.                          |
| Entity            | Profiles can be created based on different entities, for example a profile can be entity type: Company, Fund, Charity, Sole trader, Individual                              |
| Representatives   | These are people types that are associated to a profile, these can include: Directors, UBOs, Partners, Trustees etc                                                         |
| Onboarding Portal | This is the onboarding portal focused on the onboarding of the entity itself, for example an employee completing the required information on a company for their onboarding |
| Verify Portal     | A dedicated portal focused on the KYC on individuals, this portal is used anytime an Individual is performing a verification flow.                                          |


---

# 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://detected.gitbook.io/detected-docs/api-overview/terminology.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.