Skip to main content

​
Overview

nOps connects to Vercel over two REST paths and can ingest either or both:
  • Platform billing — all Vercel spend (compute, bandwidth, storage, AI, and more) delivered in the FOCUS v1.3 open cost standard, per project and per day.
  • AI Gateway usage — per-user, per-model spend and token usage for traffic routed through Vercel AI Gateway.
Each path uses its own credential, so you provide only the credentials for the data you want. All credentials are validated before save and are never shown again in the nOps UI after you connect.
The two paths use different credentials from different places in the Vercel dashboard: platform billing uses a Vercel Access Token (plus your Team ID), while AI Gateway uses a separate AI Gateway API key. You can connect one or both.

​
Prerequisites

  • A Vercel team on a paid plan. AI Gateway usage (/v1/report) requires paid Pro or Enterprise — Hobby and Pro-trial teams cannot use it. Platform billing has no charges to report on a free Hobby team.
  • Permission to create an Access Token and an AI Gateway API key for the team.
  • nOps organization administrator access to connect or manage the integration.
Members can view integration status on Account Settings and Integrations, but only admins (and owners) can connect, re-validate, or disconnect. Non-admins see an Admin Only indicator on the Vercel card.

​
Create your Vercel credentials

​
1. Vercel Access Token (platform billing)

  1. Sign in to the Vercel dashboard.
  2. Open Settings → Tokens (Account Tokens page).
  3. Click Create, enter a descriptive name (for example nOps Integration).
  4. Set Scope to the team whose billing you want to connect — not your personal account.
  5. Choose an expiration (or no expiration for a standing integration) and click Create Token.
  6. Copy the token immediately — Vercel shows it only once.
The token inherits the role of the account that creates it. To read billing, that account must have one of these team roles: Owner, Member, Developer, Security, Billing, or Enterprise Viewer. A read-only role is sufficient.

​
2. Vercel Team ID (platform billing)

Open Team Settings → General and copy the Team ID (format team_xxxxxxxx). It is also visible in the dashboard URL while you are inside the team.

​
3. AI Gateway API key (AI Gateway usage)

  1. In the Vercel dashboard, open AI Gateway → API Keys.
  2. Click Create key and follow the prompts.
  3. Copy the key immediately. The team is inferred from the key, so no Team ID is needed for this path.
Treat both credentials like passwords — do not share them in chat, email, or source control. Vercel deactivates a token and any AI Gateway keys when the member who created them leaves the team, so for a durable integration create them under a dedicated service account rather than a personal login.

​
Connect in nOps

Only nOps administrators can complete these steps.

​
Where to open Vercel

  • To connect for the first time — go to Settings → Integrations and click the Vercel card (use View all if it is not in the preview).
  • To manage an existing connection — go to Account Settings → Account Status → Connected apps and click the Vercel chip to re-validate or disconnect.

​
Connect steps

  1. Click the Vercel integration card or chip.
  2. Choose what to ingest: Platform billing, AI Gateway, or Both.
  3. Provide the matching credentials:
    • Platform billing → paste your Access Token and Team ID.
    • AI Gateway → paste your AI Gateway API key.
  4. Click Connect.
nOps validates each credential before saving:
  • Access Token → a test call to GET /v1/billing/charges for the team (with a recent date range).
  • AI Gateway key → GET /v1/credits, then GET /v1/report.
If validation succeeds, the status shows Integrated on the catalog card, or Connected in Account Status.

​
Manage your connection

After Vercel is connected, administrators can open the same card or chip to:
  • Re-validate — nOps re-checks the stored credentials without asking you to re-enter them.
  • Disconnect — removes the stored credentials and marks the integration as disconnected.
If validation fails (for example, a token was revoked), the status changes to Action required. An administrator should reconnect with new credentials, or use Re-validate after fixing them in Vercel.

​
What nOps stores

nOps saves integration status and configuration (such as which paths are enabled, the Team ID, and when Vercel was connected and last validated) so your team can see whether the integration is active. Your Access Token and AI Gateway key are stored securely and are never shown again in the nOps UI after you connect.

​
Troubleshooting

​
Invalid token or key

  • Confirm you copied the full value with no leading or trailing spaces.
  • For the Access Token, confirm it is scoped to the team (not your personal account) and that the creating account has a billing-eligible role.
  • For AI Gateway, confirm the key was created under AI Gateway → API Keys.

​
403 on AI Gateway

  • The team is on Hobby or a Pro trial, which cannot use the AI Gateway reporting API. Upgrade to paid Pro or Enterprise, then reconnect.

​
No billing data

  • Confirm the Team ID is correct and matches the token’s scope.
  • A free Hobby team has no billing charges to return — connect a paid team.
  • Allow time for the first sync to complete after connecting.

​
Action required

  • A stored credential was revoked, expired, or created by a member who left the team. Create new credentials and connect again, or use Re-validate after fixing them in Vercel.

​
Admin Only on the card

  • You are signed in as a member, not an administrator. Ask an org admin to connect or manage Vercel.

​
Still stuck?

Contact your nOps administrator or nOps support with the time of the error (never the token or key itself).

​
Reference