> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.2/built-in-connectors/vercel.md).

# Vercel

The Vercel connector for Elimity Insights fetches users, projects and teams for a Vercel account so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Setting up a dedicated user in Vercel

The Vercel connector for Elimity Insights authenticates with an access token bound to a Vercel account. We recommend creating a dedicated account with minimal access rights to the teams you want to import from. For example, you could create an `elimity-insights-vercel@<your-domain>` account and add it as a billing user to the teams you want to import from. Having set up this account, you can now create an access token as described in [the official documentation](https://vercel.com/guides/how-do-i-use-a-vercel-api-access-token#creating-an-access-token); note down the token for the next step. The connector will only import teams for which you have granted access in the token.

## 2. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Vercel source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>Gateway URL</td><td>URL of the Elimity Insights Vercel gateway; SaaS customers can stick to the default of <code>https://vercel.gateways.elimity.com</code>. On-premise customers wishing to self-host can refer to <a href="/spaces/7b6iwtH0Lr9Z5pj9MCO2/pages/fwfwTnUSjEDoV1r3Nys0">our documentation about gateways and import agents </a>for more information.</td></tr><tr><td>Access token</td><td>Token you noted down in step 1.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.elimity.com/reference-manual/v3.44.2/built-in-connectors/vercel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.