> ## 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 Blackpoint Cyber to Neo

> Create a Blackpoint CompassOne API key and save it in Neo

You connect Blackpoint once at the MSP level. One API key covers every customer tenant of your partner account.

## 1. Create the API key

**1. Open the API settings**

Sign in to the Blackpoint CompassOne portal with your partner account, and open the settings page where API keys are created. If you do not see it, ask your Blackpoint account manager to turn on API access for your account.

**2. Create the key**

Create a key for Neo on the partner account that holds your customers, not on one customer's tenant.

**3. Copy the key**

Copy the key. Store it only in Neo.

> [!WARNING]
>
> Revoking the key in CompassOne cuts Neo off at once. Save the new key here when you rotate it.

Blackpoint allows 2,000 API requests per 15 minutes per key, shared with every other tool that uses it. Neo uses at most 40 a minute.

Some data needs the matching Blackpoint product: vulnerabilities and exposures need vulnerability management, and the Cloud Response calls need a Cloud Response package for that customer. Without it, Blackpoint refuses the call and Neo says so.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Blackpoint Cyber card, under Endpoint Security.

**2. Save the key**

Paste the API key and click **Save settings**. Paste the key alone; Neo adds the `Bearer` prefix. Neo checks it against Blackpoint before saving, so a wrong key is rejected straight away.

Neo then maps your Blackpoint tenants to your PSA companies. Check the **Organization Mapping** tab on the card, and confirm or correct each suggested match.

## 3. Turn Blackpoint on per agent

Open the agent, go to its **Tools & Settings** tab, click **Endpoint Security**, and expand the **Blackpoint Cyber** block. Pick one of its **Presets**, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Accounts & Tenants** | Disabled, Read Only | Your partner account, its customer tenants and the portal's users. |
| **Detections** | Disabled, Read Only | Detections, their alerts, counts and trends. Turn on for an agent that works Blackpoint tickets. |
| **Assets** | Disabled, Read Only | Devices, users, software and sources per customer. |
| **Vulnerabilities & Exposures** | Disabled, Read Only | Vulnerabilities, scans, dark web and external exposures. |
| **Posture & Reports** | Disabled, Read Only | The posture rating and Blackpoint's reports. |
| **Cloud Response** | Disabled, Read Only, Read / Write | Microsoft 365 connections and users, approved countries and travel windows; adding or removing one. |
| **Cloud Onboarding** | Disabled, Read Only, Read / Write | Google Workspace and Cisco Duo onboardings. |
| **Escalation Contacts** | Disabled, Read Only, Read / Write | The contact groups Blackpoint's SOC calls. |

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read | Adding or removing an approved country or a travel window; no other write is allowed |
| **IT Admin** | Every read, contact groups and onboardings | Approved countries and travel windows, and removing a Duo onboarding |
| **Full Automation** | Every read and write | Removing a Duo onboarding |

See [Blackpoint API](https://docs.neoagent.io/agents/tools/security/blackpoint-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.