Cradlepoint uses one set of NetCloud API keys per MSP, made in the parent account that holds your clients’ subaccounts. Connect it once and every agent you enable can use it, with permissions you control per agent.
What Neo can do with Cradlepoint
Router & WAN Status
Read which routers are online, since when, and each WAN link’s connection state, carrier and address.
Failovers & Alerts
Read when a router failed over to its backup link, when it came back, and the router’s alerts and logs.
Signal & Speed
Read cellular signal and health, link throughput and usage, and run a speed test on a WAN link.
Changes
Reboot a router, change one setting in its configuration, move it to another group, and manage alert rules, apps and subaccounts.
Your clients’ accounts are mapped automatically
Neo matches each NCM account to a company in your PSA and keeps the mapping on the Cradlepoint card’s Organization Mapping tab. It refreshes the mapping when you save the keys, and again on each nightly PSA sync. Keep each client’s routers in its own subaccount; a client with a subaccount per site maps several accounts to one company. Matching tries the account’s name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest. A name match, or one you confirm, is handed straight to your agents, so they start from the client’s accounts without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent reaches only the accounts mapped to the ticket’s company, and the routers in them.Next steps
Connect Cradlepoint
Create NetCloud API keys in NCM, save them in Neo and turn Cradlepoint on per agent.