Skip to content

Start building

Integration · Cloud and hosting

AI agents for Fly.io

Look after apps on Fly.io through the Machines API.

Actions
10
Read
6
Write
4

Actions

What your agents can do in Fly.io

Look after apps on Fly.io through the Machines API: list apps, their Machines and volumes, read a Machine's state, config and recent events, and start, stop, restart or suspend Machines, with an organization access token.

Read 6

Look things up. Nothing changes.

  • List apps

    Lists the organization's apps, as apps: each with id, name, machine_count, volume_count and network; total_apps and next_cursor (with limit) page on.

  • Get an app

    Reads one app: id, status, organization, machine_count, volume_count and network.

  • List an app's Machines

    Lists an app's Machines, as result: each with id, name, state (created, started, stopped, suspended, destroyed …), region, image_ref, private_ip, created_at and updated_at.

  • Get a Machine

    Reads one Machine in full: state, region, image_ref, config (image, guest CPUs and memory, services, env, restart policy), health checks with their status, and recent events.

  • List a Machine's events

    Lists a Machine's latest events, as result: each with type (launch, start, stop, exit, restart, update …), status, source (user or flyd), timestamp (epoch ms) and request (like an exit code).

  • List an app's volumes

    Lists an app's volumes, as result: each with id (vol_…), name, state, region, zone, size_gb, attached_machine_id, encrypted, snapshot_retention and created_at.

Write 4

Create, change or send.

  • Start a Machine

    Starts a stopped or suspended Machine (a suspended one resumes from its snapshot when it can).

  • Stop a Machine

    Stops a running Machine: it is sent signal (SIGINT by default, or the app's kill_signal), then killed after timeout.

  • Restart a Machine

    Restarts a Machine in place (stop with signal, wait up to timeout, start again).

  • Suspend a Machine

    Suspends a running Machine, keeping a snapshot of its memory so the next start resumes quickly (Fly.io tries, but cannot promise, to resume rather than boot).

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Fly.io account.

What you enter

  • Access token

Settings

  • Organization

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Fly.io data

    Ask a question in plain words. The agent can list apps, get an app or list an app's Machines in Fly.io, then answers with what it found.

  • 02

    Let an agent update Fly.io

    Have the agent start a Machine or stop a Machine in Fly.io as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Fly.io and Slack: it can list apps in Fly.io and post a summary to a Slack channel in the same run.

FAQ

Fly.io and MyDeepAgents

Can MyDeepAgents connect to Fly.io?

Yes. The Fly.io connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Fly.io?

Paste an API key from your Fly.io account. You'll need: Access token. The connection also asks for: Organization. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Fly.io without asking?

Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs.

Can I use Fly.io in workflows as well as agents?

Yes. Every Fly.io action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Fly.io to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.