Cloud, hosting & identity · wired today
Drive Docker Hub with governed agents
Infrastructure state changes under you; agents need to read it live. The Docker Hub connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Docker Hub
| Tool | What it does |
|---|---|
list_repositories | List public Docker Hub repositories in one namespace (organisation or user), newest activity first when ordering is set |
get_repository | Get one public Docker Hub repository (short description, pull and star counts, last update) |
list_tags | List image tags for one public Docker Hub repository (tag name, size, digest, last push) |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Docker Hub connector needs
You provide username, access token from your Docker Hub 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: Docker Hub's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Docker Hub 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.
Docker Hub integration FAQ
What can Quox agents do with Docker Hub?
Agents can run 3 read-only tools against Docker Hub: list repositories, get repository, list tags. Every call is receipted in the evidence trail.
What does the Docker Hub integration need?
You provide username, access token from your Docker Hub 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 Docker Hub 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 Docker Hub connector?
This connector was blind shape-proven against the real Docker Hub 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.