Can AI agents automate Fly.io?

Fly.io is automatable today through the Machines API. The public base URL is https://api.machines.dev. Requests send Authorization Bearer with a Fly.io access token. Tokens are macaroons. flyctl can mint app-scoped deploy tokens, org-scoped tokens, read-only org tokens, SSH tokens, and machine-exec tokens. The default lifetime is 20 years, and the docs recommend a shorter expiry. The personal fly auth token is short-lived and is not the recommended automation credential. The API covers apps, Machines, and volumes. Create, start, and similar actions are limited to 1 request per second per action, with a short burst. Sprites use a separate credential and a separate API at https://api.sprites.dev/v1. flyctl installs on macOS, Linux, and Windows. FLY_API_TOKEN runs fly deploy without a browser login. fly mcp server exposes apps, certs, logs, machines, orgs, platform, secrets, status, and volumes. It binds to 127.0.0.1 by default. Sprites has a hosted MCP server at https://sprites.dev/mcp with OAuth, PKCE S256, and scopes sprites:read and sprites:write. Compute is billed by the second. The pricing page does not publish a free Machines plan. New Sprites organizations get $30 in trial credit. https://docs.fly.io/llms.txt is a first-party documentation index. Zapier, Make, Power Automate, and n8n were not assessed. A published language SDK was not established. Computer-use viability is unassessed. API scores 8. CLI scores 8. MCP scores 7. API is the best path because a bearer token calls the Machines API directly, without a local flyctl install or an MCP client.

Best path today: api · Overall automatability: 8/10