> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect Addigy to Neo Agent for Apple device context

Addigy manages Apple devices only. Neo connects to it with one API key, and every call goes to Addigy's cloud API, so there is no server URL to enter.

## Setup

<CardGroup cols={2}>
  <Card title="Creating an API key" icon="key" href="/integrations/rmm/addigy/creating-api-key">
    Create an API v2 key in Addigy with the permission Neo needs.
  </Card>

  <Card title="Connecting to Neo Agent" icon="link" href="/integrations/rmm/addigy/connecting-to-neo">
    Paste the key into the Addigy card on the Neo Integrations page.
  </Card>
</CardGroup>

## Prerequisites

* An Addigy user in your top-level organization who can create API keys. Addigy asks for the **View Integrations API Keys** and **Create Integrations API Keys** user permissions.

## What Neo does with Addigy

* **Device sync**: on each sync, Neo reads every device in the key's organization and in each of its child organizations.
* **Device lookup**: while it works a ticket, an agent reads the details of a device in the key's organization, and the installed software of a Mac.
* **Company mapping**: Neo links each synced device to its PSA company through your Addigy client organizations and policies. A device in a child organization maps through that organization. Any other device in exactly one policy maps through the top-level policy above it, and a device in several policies has no policy route. If Addigy's own Autotask or ConnectWise integration links those policies to an account in your active PSA, Neo uses that link. See [Device mapping](/integrations/rmm/device-mapping) to check and correct the result.

## No Windows devices

Neo flows that need a Windows machine, such as [on-prem AD and Exchange](/integrations/m365/on-prem), cannot run through Addigy. Connect a second RMM for those devices: Neo [connects several RMMs at once](/integrations/rmm/intro), and each device stays with the RMM it came from.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.