Evaluate a BigFix session relevance query on the root server.

Session relevance queries data the server already has (computers, fixlets, actions, sites, operators...) with no client round-trip. Examples: 'number of bes computers', '(name of it, id of it) of bes computers whose (now - last report time of it < 1 * day)'.

There is no server-side result limit, so bound large result sets in the relevance itself (e.g. 'firsts 100 of bes computers'). Returns the raw JSON envelope: {"result": [...], "evaltime_ms": ...}.

Results are evaluated within the configured operator's scope. Unless whoami reports is_main_operator, counts and lists are a lower bound on what exists - report them as visible to this operator, not as the complete state of BigFix.

Submit a BigFix client (fast) query. Targeting: set exactly one of target_all, target_computer_ids, target_computer_names, or target_relevance (client relevance evaluated on each agent to decide applicability). Targeting is limited to the configured operator's scope, so target_all means all computers this operator can see, not necessarily all computers in BigFix.

Fetch current results for a previously submitted client fast query.

Results are cumulative and there is no completion flag: safe and cheap to call repeatedly until reported_count stops growing or the expected number of computers have reported.

Submit a BigFix client (fast) query and wait for results, polling until done or timeout. Targeting: set exactly one of target_all, target_computer_ids, target_computer_names, or target_relevance (client relevance evaluated on each agent to decide applicability). Targeting is limited to the configured operator's scope, so target_all means all computers this operator can see, not necessarily all computers in BigFix.

Get BigFix root server info (version, etc) from /api/serverinfo.

List all sites visible to the configured operator.

Look up a computer group by name within an explicit site path.

Implemented against /api/computergroups/{site_path} directly rather than besapi's get_computergroup, which routes through the mutable "current site path" connection state this server avoids.

Look up a BigFix operator (console user) by name.

Read a BigFix dashboard datastore variable value (read-only).

Show the configured connection: user, root server, main operator status.

Cheap connectivity and permission smoke test. is_main_operator tells you whether results from the other tools can be treated as the full state of BigFix (master operator) or only as this operator's scoped view, which may be incomplete in ways this operator cannot detect.

Read-only escape hatch: GET any BigFix REST API path under /api/.

GET is non-mutating across the BigFix REST API. Use path 'help' to discover available endpoints. Response text is truncated to 50KB.