Developer & CI · wired today
What can agents actually do with Kong?
Build, review and release state is where agents earn their keep. The Kong 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.
The Kong tool list, exactly as agents see it
get_status— Get the Kong node's health: connection and request counters, datastore reachability, and the loaded configuration hash in DB-less modenode_info— Identify the Kong node this credential points at: gateway version, hostname, node id, Lua runtime and the plugins enabled across the clusterlist_services— List the services configured on this Kong gateway, with their upstream target and timeoutslist_routes— List the routes configured on this Kong gateway, with the hosts, paths and methods each one matches and the service it forwards tolist_plugins— List the plugins configured on this Kong gateway, with what each one is attached to and whether it is enabled (plugin config is deliberately not returned)
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Kong connector needs
You provide admin URL, API key from your Kong 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: Kong'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 Kong 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.
Kong integration FAQ
What can Quox agents do with Kong?
Agents can run 5 read-only tools against Kong: get status, node info, list services, list routes, list plugins. Every call is receipted in the evidence trail.
What does the Kong integration need?
You provide admin URL, API key from your Kong 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 Kong 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 Kong connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Kong 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.