Skip to content

Get Agent Operators Summary

GET
/agent/operators/summary

One digest across the whole bench.

Finding counts here are DISTINCT, not the sum of the per-operator numbers from GET /agent/operators. Shared findings legitimately appear in several operators’ caches, and adding the cards up counts them more than once - the app’s own banner did exactly that before this was split out.

Authorizations

Parameters

Header Parameters

X-Target-Org-Id
Any of:
string

Responses

200

Successful Response

object
data
required

An open envelope for one operator answer.

Open because an operator’s health snapshot, scorecard and catalog are per-operator documents whose shape follows what that operator monitors - the revenue operator reports different checks from the deliverability one, and both grow. On an OVERSIGHT surface a dropped field reads as “nothing to worry about” rather than “we did not tell you”, which is the failure mode worth designing against.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string