Cloud, hosting & identity · wired today
Drive Fly.io with governed agents
Infrastructure state changes under you; agents need to read it live. The Fly.io 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.
What agents can run against Fly.io
| Tool | What it does |
|---|---|
list_apps | List Fly.io apps in one organisation, with machine and volume counts |
get_app | Get one Fly.io app by name, including status and machine count |
list_machines | List the Fly Machines belonging to one app, optionally filtered by state or region |
get_machine | Get one Fly Machine by ID within an app, including state and image |
list_volumes | List the Fly volumes belonging to one app, with size and attachment state |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Fly.io connector needs
You provide API token from your Fly.io 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: Fly.io's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Fly.io 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.
Fly.io integration FAQ
What can Quox agents do with Fly.io?
Agents can run 5 read-only tools against Fly.io: list apps, get app, list machines, get machine, list volumes. Every call is receipted in the evidence trail.
What does the Fly.io integration need?
You provide API token from your Fly.io 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 Fly.io 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 Fly.io connector?
This connector was blind shape-proven against the real Fly.io 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.