# Vercel

{% hint style="info" %} <sub>If your demo depends on a live URL, Vercel health is not optional polish. It is part of the proof chain.</sub>
{% endhint %}

<h2 align="center"><sub>This page means</sub></h2>

<table><thead><tr><th width="287.6363525390625">This page is</th><th>This page is not</th></tr></thead><tbody><tr><td><sub>Operator guidance for the Vercel slot</sub></td><td><sub>Vercel’s full billing and limits documentation</sub></td></tr><tr><td><sub>Save, Test, rotate habits</sub></td><td><sub>A guarantee that every build will pass on the first try</sub></td></tr></tbody></table>

<h3 align="center"><sub>How to get a Vercel token for ARIA</sub></h3>

{% stepper %}
{% step %} <sub>**Pick the right scope (personal account)**</sub>

<sub>If your apps live under a Vercel team, switch to that team in the dashboard before you create the token, or create a team scoped token from team settings. Wrong scope is the most common “Test looked fine until deploy” bug.</sub>
{% endstep %}

{% step %} <sub>**Open Tokens**</sub>

<sub>**From the Vercel UI:**</sub> \ <sub>**>**</sub> <sub>**Click on your username**</sub> <sub></sub><sub>at the bottom left of the side menu.</sub>\
![](/files/EZT8YQlveeFaf73l0oe9)\ <sub>**> Click again on your username/email (Account Settings)**</sub>\ <sub>**> Then**</sub> <sub>**Tokens**</sub> <sub></sub><sub>for personal scope, or</sub> <sub></sub><sub>**Team Settings**</sub> <sub></sub><sub>then</sub> <sub></sub><sub>**Tokens**</sub> <sub></sub><sub>for team scope (labels may vary slightly by Vercel UI version).</sub>\
![](/files/2doQPJRKpNmZEfAQAC8d)
{% endstep %}

{% step %} <sub>**Create and name the token**</sub>

<sub>Use a name you will recognize in an audit log, for example</sub> <sub></sub><sub>`aria-prod-build-2026`</sub><sub>. Create the token and copy the value immediately. Vercel shows it once.</sub>\
![](/files/akF0C2flSQ8mjWhWTGqI)
{% endstep %}

{% step %} <sub>**Paste in ARIA & Test**</sub>

<sub>In ARIA</sub> <sub></sub><sub>**Settings**</sub><sub>, open</sub> <sub></sub><sub>**Vercel API Token**</sub><sub>, paste,</sub> <sub></sub><sub>**Save**</sub><sub>, then</sub> <sub></sub><sub>**Test**</sub><sub>. Confirm the success message references the account or team you expect.</sub>
{% endstep %}
{% endstepper %}

***

<h2 align="center"><sub>Ask a question</sub></h2>

<p align="center"><sub><strong>Which preview URL are you willing to put on a slide tomorrow?</strong></sub> <br><sub>If you cannot name it, configure Vercel before you tune copy.</sub></p>

### Official Vercel links

<table><thead><tr><th width="198.54547119140625">Resource</th><th>URL</th></tr></thead><tbody><tr><td><sub>Account tokens</sub></td><td><a href="https://vercel.com/account/tokens"><sub>https://vercel.com/account/tokens</sub></a></td></tr><tr><td><sub>Vercel dashboard</sub></td><td><a href="https://vercel.com/dashboard"><sub>https://vercel.com/dashboard</sub></a></td></tr><tr><td><sub>Docs: creating a token</sub></td><td><a href="https://vercel.com/docs/rest-api#creating-an-access-token"><sub>https://vercel.com/docs/rest-api#creating-an-access-token</sub></a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.ariaagi.com/settings-and-integrations/vercel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.