> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/api-documentation/object-structures.md).
# Object Structures
PlexTrac data is categorized into clients, reports, findings, and assets, which are the primary containers holding information stored in Plextrac. The Clients module holds assets and reports, while reports hold findings.
While these objects exist as their type in the database, some fields about an object are stored both on the object and as values inside other objects. The most common example of this is affected assets and vulnerabilities.
Here is a list of object structures that have been defined:
* [Client Object](/plextrac-documentation/api-documentation/object-structures/client-object.md)
* [Report Object](/plextrac-documentation/api-documentation/object-structures/report-object.md)
* [Finding Object](/plextrac-documentation/api-documentation/object-structures/finding-object.md)
* [Asset Object](/plextrac-documentation/api-documentation/object-structures/asset-object.md)
* [Client Asset](https://docs.plextrac.com/plextrac-documentation/master/plextrac-api-overview/object-structures/asset-object#child-asset-structure)
* [Affected Asset (finding asset)](https://docs.plextrac.com/plextrac-documentation/master/plextrac-api-overview/object-structures/asset-object#affected-asset-structure)
* [Evidence Object](/plextrac-documentation/api-documentation/object-structures/evidence-object.md)
---
# 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.plextrac.com/plextrac-documentation/api-documentation/object-structures.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.
