Cloud, hosting & identity · wired today
What can agents actually do with Railway?
Infrastructure state changes under you; agents need to read it live. The Railway 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 Railway tool list, exactly as agents see it
me— Get the Railway account the API token belongs to (who am I)list_projects— List Railway projects visible to the token (id, name, description, created and updated times)get_project— Get one Railway project by id, with the services and environments it containsget_service— Get one Railway service by id (name, icon, owning project, creation time)list_deployments— List deployments for one Railway service, newest first (status, url, creation time)
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Railway connector needs
You provide token from your Railway 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: Railway's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Railway 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.
Railway integration FAQ
What can Quox agents do with Railway?
Agents can run 5 read-only tools against Railway: me, list projects, get project, get service, list deployments. Every call is receipted in the evidence trail.
What does the Railway integration need?
You provide token from your Railway 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 Railway 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 Railway connector?
This connector was blind shape-proven against the real Railway 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.