Developer & CI · wired today
Drive CircleCI with governed agents
Build, review and release state is where agents earn their keep. The CircleCI 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.
What agents can run against CircleCI
| Tool | What it does |
|---|---|
get_me | Get the CircleCI user account that owns the configured API token |
list_pipelines | List recent CircleCI pipelines for one project, newest first, optionally filtered to a branch |
get_pipeline | Get one CircleCI pipeline by its pipeline id |
list_workflows | List the workflows belonging to one CircleCI pipeline, with their current status |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the CircleCI connector needs
You provide token from your CircleCI 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: CircleCI's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real CircleCI 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.
CircleCI integration FAQ
What can Quox agents do with CircleCI?
Agents can run 4 read-only tools against CircleCI: get me, list pipelines, get pipeline, list workflows. Every call is receipted in the evidence trail.
What does the CircleCI integration need?
You provide token from your CircleCI 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 CircleCI 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 CircleCI connector?
This connector was blind shape-proven against the real CircleCI 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.