Monitoring & incidents · wired today

OpsGenie, wired into your agent workforce

Incidents move faster than humans can tab-switch. The OpsGenie connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.

Connecting OpsGenie takes one credential

You provide API key from your OpsGenie 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: OpsGenie's own API documentation ↗ covers creating and scoping the credential.

What agents can run against OpsGenie

list_alerts

List Opsgenie alerts, optionally filtered by a search query and sorted

get_alert

Get a single Opsgenie alert by id

list_teams

List Opsgenie teams

list_schedules

List Opsgenie on-call schedules

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

This connector was blind shape-proven against the real OpsGenie API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

OpsGenie integration FAQ

What can Quox agents do with OpsGenie?

Agents can run 4 read-only tools against OpsGenie: list alerts, get alert, list teams, list schedules. Every call is receipted in the evidence trail.

What does the OpsGenie integration need?

You provide API key from your OpsGenie 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 OpsGenie 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 OpsGenie connector?