Developer & CI · wired today
What can agents actually do with Netlify?
Build, review and release state is where agents earn their keep. The Netlify 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.
The Netlify tool list, exactly as agents see it
get_user— Get the Netlify account that owns the configured access tokenlist_sites— List Netlify sites the token can see, optionally filtered by a site name substringget_site— Get one Netlify site by its site idlist_deploys— List deploys for one Netlify site, newest first
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Netlify connector needs
You provide token from your Netlify account; Quox sends it as a bearer token. 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: Netlify's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Netlify 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.
Netlify integration FAQ
What can Quox agents do with Netlify?
Agents can run 4 read-only tools against Netlify: get user, list sites, get site, list deploys. Every call is receipted in the evidence trail.
What does the Netlify integration need?
You provide token from your Netlify account; Quox sends it as a bearer token. 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 Netlify 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 Netlify connector?
This connector was blind shape-proven against the real Netlify 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.