# Which Beam API to use

The Beam APIs cover device-local channels and cloud management of devices, sites, and networks.

<table>
  <thead>
    <tr>
      <th>Workflow</th>
      <th>API</th>
      <th>Guide</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Create, control, and monitor channels on a Beam device</td>
      <td>Channels</td>
      <td><a href="/beam/api-guides/how-to/channels">Channel workflows</a></td>
    </tr>
    <tr>
      <td>Register devices, manage software, and back up or restore configurations</td>
      <td>Fleets</td>
      <td><a href="/beam/api-guides/how-to/fleets">Fleet workflows</a></td>
    </tr>
    <tr>
      <td>Configure networks and sites for devices</td>
      <td>Infrastructure</td>
      <td><a href="/beam/api-guides/how-to/infrastructure">Infrastructure workflows</a></td>
    </tr>
  </tbody>
</table>

## Cloud management

Use Infrastructure to define sites and networks, then Fleets to register and operate devices. The [API overview](/beam/api-guides/understanding/overview) describes their project-scoped connections.

## Device-local channels

The Channels API runs on the Beam device. Start with [Connect to a Beam device](/beam/api-guides/how-to/channels/connect-to-a-device), then [Manage channels](/beam/api-guides/how-to/channels/manage-channels).

## Related account setup

The [Management API guides](/mkio/api-guides/how-to/management) cover organizations, projects, users, and tokens.