Monitoring & incidents · wired today
Drive PagerDuty with governed agents
Incidents move faster than humans can tab-switch. The PagerDuty connector is one of 205 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against PagerDuty
| Tool | What it does |
|---|---|
list_incidents | List PagerDuty incidents, optionally filtered by status and sorted |
get_incident | Get a single PagerDuty incident by id or incident number |
list_services | List PagerDuty services |
list_oncalls | List who is currently on call, optionally limited to specific schedules |
list_schedules | List PagerDuty on-call schedules |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the PagerDuty connector needs
You provide API key from your PagerDuty account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: PagerDuty's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
PagerDuty answers every unauthenticated request identically, so its endpoint paths rest on PagerDuty's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
PagerDuty integration FAQ
What can Quox agents do with PagerDuty?
Agents can run 5 read-only tools against PagerDuty: list incidents, get incident, list services, list oncalls, list schedules. Every call is receipted in the evidence trail.
What does the PagerDuty integration need?
You provide API key from your PagerDuty account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my PagerDuty credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the PagerDuty connector?
PagerDuty answers every unauthenticated request identically, so its endpoint paths rest on PagerDuty's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.