> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/sprinto-ai/ai-playground/supported-entity-types-and-attributes.md).

# Supported entity types & attributes

Overview of Supported Entity Types for AI Playground and Ask AI

This reference provides a complete list of entity types that the **Sprinto AI** call-to-action (CTA) supports—such as **Custom Check, Endpoint, Incident, Infra Entity**, and more. Use it to understand:

* **Where the Sprinto AI CTA is available:** Quickly locate the CTA across all supported entities.
* **Contextual access for AI:** See which attributes and data points are accessible to AI for each entity type, and which remain outside its scope.
* **Support status:** The **Support** column clearly indicates whether an entity is **Fully Supported**, **Partially Supported**, or **Unsupported**.
  * For **Partially Supported** entities, the table details which attributes are currently unavailable and provides the estimated timeline (ETA) for when full support will be added.
  * For **Unsupported** entities, it also provides the planned ETA for when support will be introduced.

The following table ensures you know exactly what Sprinto AI can leverage today for AI Actions and for any questions you ask, and what enhancements are planned.

<table><thead><tr><th width="142.19140625">Entity type</th><th>Placement</th><th>Support</th></tr></thead><tbody><tr><td>Custom Check</td><td><ol><li>Data library > Workflow check</li><li>Data library > Monitoring  > Workflow checks</li><li>Entity > Monitoring  > Workflow checks</li></ol></td><td>Supports all attributes</td></tr><tr><td>Endpoint</td><td>Data library > Staff device > device</td><td>Supports all attributes</td></tr><tr><td>Incident</td><td>Data library > Incidents > Incident monitoring source > Incident</td><td>Supports all attributes</td></tr><tr><td>Infra Entity</td><td>Data library > Infrastructure > InfraEntity </td><td>Supports all attributes</td></tr><tr><td>Org Risk Item</td><td>Risks > Risk register > Risk</td><td><p>Supports all attributes apart from:</p><ol><li>Mapped controls - ETA to go live: 19th September'25.</li><li>Risk tasks -ETA to go live: 19th September'25.</li><li>Custom fields -ETA to go live: 26th September'25.</li><li>Custom risk formula -ETA to go live: 26th September'25.</li></ol></td></tr><tr><td>Pentest</td><td>Data library > Vulnerabilities > Pentest > Pentest report</td><td>Supports all attributes</td></tr><tr><td>Policy</td><td>Policies > Policy</td><td><p>Supports all attributes apart from:</p><ol><li>Mapped frameworks - ETA to go live: 19th September'25.</li><li> Mapped controls - ETA to go live: 19th September'25.</li></ol></td></tr><tr><td>Pull Request</td><td>Data library > Change management > Repo providers > 'Peer reviews' tab > Peer review</td><td>Supports all attributes</td></tr><tr><td>Repo</td><td>Data library > Change management > Repo providers > Repos monitored</td><td>Supports all attributes</td></tr><tr><td>Repo Branch</td><td>Data library > Change management > Repo providers > Integration branches</td><td>Supports all attributes</td></tr><tr><td>Ticketing Ticket</td><td>Data library > Change management > Ticket providers > 'Tickets' tab > Ticket</td><td>Supports all attributes</td></tr><tr><td>User</td><td>Data library >People > Staff</td><td><p>Supports all attributes apart from:</p><ol><li>Custom fields -ETA to go live: 26th September'25.</li><li>Background verification via Checkr, SpringVerify, Ongrid, Certn -ETA to go live: 26th September'25.</li><li>Reporting manager details -ETA to go live: 26th September'25.</li></ol></td></tr><tr><td>Vendor</td><td>Data library > Vendors > All vendors > Vendor</td><td><p>Supports all attributes apart from:</p><ol><li>Custom fields -ETA to go live: 26th September'25.</li><li>Risk scores -ETA to go live: 26th September'25.</li><li>Findings -ETA to go live: 26th September'25.</li><li>Tasks -ETA to go live: 26th September'25.</li></ol></td></tr><tr><td>Vulnerability</td><td>Data library > Vulnerabilities > Vulnerability monitoring system > Vulnerabilities tab > Vulnerability</td><td>Supports all attributes</td></tr><tr><td>Access</td><td>Data library > Access > Critical systems > Critical system</td><td>Not supported, ETA to go live: 19th September'25</td></tr><tr><td>Audit</td><td>Audits > Overview > Audit</td><td>Not supported, ETA to go live: 26th September'25</td></tr><tr><td>Control</td><td>Compliance > Controls > Control</td><td>Not supported, ETA to go live: 19th September'25</td></tr><tr><td>Evidence</td><td>Audits > Evidences > Evidence</td><td>Not supported, ETA to go live: 26th September'25</td></tr><tr><td>Framework</td><td>Compliance > Frameworks > Framework</td><td>Not supported, ETA to go live: 19th September'25</td></tr></tbody></table>


---

# 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.sprinto.com/sprinto-ai/ai-playground/supported-entity-types-and-attributes.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.