Get the AI finding an AI tools ticket was opened for
Start here when working an AI tools ticket: it answers what the ticket is about. Return as JSON the device and its owner, the rule (code, title, description, severity), the one finding the ticket tracks as the device still reports it, with what it is on, its evidence (what fleetd saw behind it: runtimeFlags null when the agent’s command line was not seen, fromWebstore: true a store extension a policy or another program installed), its path (the home folder written ~) and the tool’s policy, and the ticket itself: who opened it (policy, admin, agent) and, once Primo closed it, when and why. Its comments and status are getTicket. A 404 is final: the ticket is not an AI tools ticket, or the device no longer reports its finding (Primo then closes the ticket on the next sync); a retry returns the same 404. For the whole inventory of the device, getAiToolsDevice. AI tools are what Primo finds on Macs (assistant apps, coding agents, IDE plugins, browser extensions, MCP servers, AI connections, agent instruction files), as of the last sync (lastSyncedAt of getAiToolsOverview), with Primo’s severities, less the findings the company’s AI tools settings ignore. They are not the software catalog (getSoftwares, getDeviceSoftware), the company’s own AI agents (listAgents) nor AI credits (getAiUsage). A company without AI tools monitoring gets a 403, final.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Path Parameters
Response
Primo's code of the risk, e.g. plaintext_secret
Primo's severity of the rule
critical, high, medium, low The severity in words, e.g. Critical
What the rule means in a few words; the code itself for a rule Primo has not rated yet
One line on what the rule detects
The finding the ticket tracks, as the device still reports it, with its path (the home folder written ~)