> ## 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.

# Connecting Cradlepoint to Neo

> Create NetCloud Manager API keys, and optionally an API v3 token, and save them in Neo

You connect Cradlepoint once at the MSP level. The keys act in the NCM account you create them in and in every subaccount under it, with the role you give them.

## 1. Create the API keys

**1. Open the NetCloud API page**

Sign in to NetCloud Manager in the parent account that holds your clients' subaccounts. Open **Tools** and find the **NetCloud API** section.

**2. Add an API key**

Add an API key and pick its role. **Read Only** lets Neo read routers, status, failovers and alerts. To reboot routers, run speed tests or change settings, give it **Full Access**. Reading Wi-Fi passwords needs an **Administrator** key.

**3. Copy the four values**

Copy **X-CP-API-ID**, **X-CP-API-KEY**, **X-ECM-API-ID** and **X-ECM-API-KEY**.

**4. Optional: create an API v3 token**

On the same page, create an API v3 token. Neo uses it for subscriptions, Starlink, LAN clients, modem upgrades and eSIM, Remote Connect, NetCloud Exchange, private cellular, users and Wi-Fi passwords. Without it, Neo reads and changes everything else.

## 2. Add the keys in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Cradlepoint card, under Networking.

**2. Save the keys**

Paste the four values, and the **API v3 Token** if you made one, and click **Save settings**. Neo checks them against NCM before saving, so a wrong value is rejected straight away.

## 3. Turn Cradlepoint on per agent

Open the agent, go to its **Tools & Settings** tab, click **Networking**, and expand the **Cradlepoint** block. Pick a preset, or set each area yourself:

| Preset | What it does |
| - | - |
| **Read Only** | Reads routers, status, failovers, configuration, alerts, apps, accounts, subscriptions and users. Wi-Fi passwords stay off. |
| **Helpdesk** | Reads on its own. A reboot, a speed test, a configuration change or any other router change asks a technician first. Wi-Fi passwords stay off. |
| **IT Admin** | Router, configuration, reboot, speed test, alert, app, modem and account changes run on their own. Users, Remote Connect, NetCloud Exchange and licensing ask a technician first. |
| **Full Automation** | Every change runs on its own, except the ones that always ask. |

These always ask a technician, whatever the preset: unregistering a router, deleting an account, an organization migration, any change to a user or a role, and any change that sends a password, a Wi-Fi key or a secret. Neo never sends a change that replaces a router's whole configuration, because that resets every setting it leaves out; it changes only the settings the ticket names.

## Use it on NCM alert tickets

NCM emails its alerts, such as "NCM Alert: Failover Event Occurred \[router]" and "NCM Alert: Ethernet WAN Disconnected \[router]", and they open tickets on the client's company. An agent on such a ticket finds the router the alert names in the client's mapped accounts, reads whether it still runs on its backup link or the WAN link is still down, since when, and which other link carries the site, and notes it on the ticket. Map each client's accounts on the Organization Mapping tab first: on a ticket, the agent reads only the accounts mapped to the ticket's company.

A chat or a scheduled agent with no ticket can read every account, for example to list the routers that are offline.

## Speed tests

A speed test runs NCM's TCP test against a netperf server you run, and uses the link's data, cellular data included. Name the server in the agent's instructions.

See [Cradlepoint API](https://docs.neoagent.io/agents/tools/networking/cradlepoint-api.md) for what the agent can read and change.


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