Monitoring & incidents · wired today
Drive NATS with governed agents
Incidents move faster than humans can tab-switch. The NATS connector is one of 222 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 NATS
| Tool | What it does |
|---|---|
server_info | Get the NATS server's identity, version, resource usage and message/connection totals |
connections | List the client connections currently open on this server |
subscriptions | Get subscription counts and interest-cache stats for this server |
jetstream | Get JetStream usage: memory and storage totals, accounts, streams, consumers and message/byte counts |
routes | List the cluster routes this server knows about |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the NATS connector needs
You provide base URL from your NATS account; Quox sends it as a credential embedded in the endpoint path. 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: NATS's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running NATS instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Read-only It ships read tools only, so there is nothing to approval-gate.
- Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
- Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
- Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.
NATS integration FAQ
What can Quox agents do with NATS?
Agents can run 5 read-only tools against NATS: server info, connections, subscriptions, jetstream, routes. Every call is receipted in the evidence trail.
What does the NATS integration need?
You provide base URL from your NATS account; Quox sends it as a credential embedded in the endpoint path. 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 NATS 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 NATS connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running NATS instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.