Agent Intersections
Who else is talking to this agent's audience, and how often they collide.
An operator turning on a programme needs to see the overlap BEFORE choosing a group and a priority; without it the only feedback available is a customer receiving two messages. So this uses the same window and the same claim definition the runner arbitrates on (see services/exclusivity), and the number read here is the number the runner would act on.
An agent with no group still gets a meaningful preview: the workspace default window is used, which is what the pair would be arbitrated with the moment somebody groups them.
Path parameters
Query parameters
Headers
Bearer <token>
Bearer <token>
Response
Successful Response
Changes
Changed in 3 of the 4 revisions of this API.5
- ○
the
response's property default value changed from{"request_id":"","timestamp":"2026-09-03T04:12:49.531787"}to{"request_id":"","timestamp":"2026-09-03T19:42:04.697120"}for the statusresponse-property-default-value-changed
- ○
the
response's property default value changed from2026-09-03T04:12:49.531787to2026-09-03T19:42:04.697120for the statusresponse-property-default-value-changed
- ○
- ○
the
response's property default value changed from{"request_id":"","timestamp":"2026-09-02T16:58:28.431377"}to{"request_id":"","timestamp":"2026-09-03T04:12:49.531787"}for the statusresponse-property-default-value-changed
- ○
the
response's property default value changed from2026-09-02T16:58:28.431377to2026-09-03T04:12:49.531787for the statusresponse-property-default-value-changed
- ○
- ○
endpoint added
endpoint-added
- ○