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

# Request an integration

> Name a tool Neo does not support yet, and Neo's team reviews it for a native integration

Neo's team reviews each request. When the vendor has a usable API, the team builds the integration from it within 5 working days, with permission groups, technician approval for writes and a setup guide, like the native integrations Neo already has. When it is ready, it appears in the **Directory** and you connect it there.

## Send a request

Open [**Integrations**](https://dashboard.neoagent.io/integrations?tab=directory\&build=) and click **Neo builds it**. You can also click the first tile in the **Directory** tab. If you search for a tool that Neo does not list, that tile offers to build it, with your search already filled in.

The form asks for:

| Field | What to give |
| - | - |
| **Tool or vendor** | The product name, e.g. "SecureShield AV". |
| **What should Neo do with it?** | The work you want agents to do there, in your own words. For example: "When a user reports a blocked email, release it from quarantine and allow the sender." |
| **Read only** or **Read and write** | Read only when agents only look things up; read and write when they must also change things there. |
| **Link to its API docs** | Optional. The vendor's API reference, if you know it. |
| **API spec file** | Optional. An OpenAPI, Postman, PDF or text file, up to 10 MB. |
| **I can give Neo a test API key when asked** | Optional. A test key lets Neo check the integration against your account before it ships. |

Click **Build integration** to send it.

You can also ask the Neo Support agent: "Can Neo connect to SecureShield AV?" If Neo does not support the tool, the agent confirms the details with you and sends the same request.

<Info>
  Your team can send 5 requests in any 7 days.
</Info>

## What happens next

* Neo's team reviews every request. When the vendor has a usable API, Neo builds the integration within 5 working days of the request; a request from several MSPs for the same tool is built once.
* A vendor whose API needs a partner agreement, or has no public API, can take longer or be out of reach.
* If Neo already supports the tool, we tell you in your Neo support chat where to connect it.
* If the tool is your own or an in-house API, connect it with [Custom API](/integrations/custom-api/overview), which works with any REST API.

## Through the API

`POST /public-api/integrations/requests` sends a request. See the [API introduction](/developers/introduction) for keys and the reference.


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