Analyze a failed deploy with AI
The AI reads the failed deploy's log, the failing containers' latest output, the names of the source's files, the compose file and the app's variables (never a secret's value), looks further with the read-only API tools when it needs to, and lists what went wrong. A problem's `changes` would fix it: a variable that isn't secret set to a value, a variable renamed (its value moves with it, secret or not), or new scale factors. Nothing is changed: apply them with createVar, updateVar and updateApp, then deploy again. Counts against the caller's 60 AI answers an hour.
Authorization
cloady Personal API token (cldy_…)
In: header
Path Parameters
Query Parameters
Value in
- "production"
- "preview"
- "development"
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/workspaces/string/apps/string/deploys/string/analyze"{ "problems": [ { "id": "string", "severity": "error", "title": "string", "detail": "string", "line": -9007199254740991, "fix": "string", "changes": [ { "kind": "setVar", "key": "string", "value": "string" } ] } ]}Roll an app back to a previous deploy's image POST
Needs a running, build-backed app whose target image is still in the registry. Restarts every service in the instance, database included.
Read the active deploy GET
Read the app's in-flight deploy, or its latest when none is running. Returns one `{ts, deploy}` frame: the active deploy if one is running, otherwise the most recent, and `deploy` is null when the app has never deployed. Sending `Accept: text/event-stream` instead follows it live, a frame every two seconds, closing after one terminal frame.