Jamf Pro

Vendor key: jamf_pro. For how source fields and scan configs fit together, see Agent Discovery Integrations.

Discovers agentic coding tools, autonomous local agents, AI browsers and browser extensions on your managed Macs. The Arthur discovery collector runs on each Mac and reports through a Jamf Extension Attribute. Arthur reads those results from the Jamf Pro API. Arthur makes read-only API calls and never runs anything on a device.

Before you start

Create the Arthur Extension Attribute in Jamf Pro.
Deploy the Arthur discovery collector with a Jamf policy.
Create an API role and API client in Jamf Pro (Settings → API roles and clients) with the privileges below, and generate a client secret.

For step-by-step instructions, see the Jamf Pro setup guide.

Source fields

Field	Required	Sensitive	Default	Description
`base_url`	Yes	No		Your Jamf Pro URL, for example `https://yourcompany.jamfcloud.com`. Must be `https://`.
`client_id`	Yes	Yes		The Jamf Pro API client ID.
`client_secret`	Yes	Yes		The Jamf Pro API client secret.
`include_groups`	No	No	All computers	Comma-separated computer group names. Only computers in at least one of these groups are scanned.
`exclude_groups`	No	No	None	Comma-separated computer group names. Computers in any of these groups are skipped. If a computer is in both lists, it's excluded.

A group name that doesn't exist in Jamf Pro fails the scan rather than being skipped. Otherwise a mistyped group name could quietly widen or empty the scan.

Scan config

Setting	Value
`query`	`""` to use Arthur's built-in agent catalog, or your own catalog YAML.
`query_language`	`none`
`lookback_window_seconds`	Only Macs that reported to Jamf within this window are read. `0` reads every computer.

Required permissions

The API role needs:

Read Computers
Read Smart Computer Groups and Read Static Computer Groups. Needed only if you set include_groups or exclude_groups.