Skip to content
Gauge

ax-check.com

by Gauge

Vercel

vercel.com

ax-check.com

Checked 19 September 2026

A

100/100

Agents need your login

Vercel's docs, CLI, and pricing are all clear to agents out of the box.

All 23 checked items passed: setup guide, CLI install, OpenAPI/MCP docs, and pricing tables all readable without login or interaction.

1 fix to start with

Concrete changes, backed by what we found.

Onboarding

Give agents a clear login handoff and a way to resume setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Recorded coding sessions

Same task, 3 models, no vercel.com account. Recorded 19 September 2026 on Pi.

3 recorded · 1m 35s

1m 35s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Vercel. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user is asking me to build a simple example using Vercel. Let me first check the repository, and then think about whether there's a developer workflow I can tackle for this product.

Let me look at the current working directory and check what's available—credentials, environment variables, etc.

$ ls -la /sandbox/repo && env | grep -iE 'vercel|token|api_key' | sed 's/=.*/=<set>/'{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 08:27 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 08:27 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore\nPI_GATEWAY_API_KEY=<set>\n","type":"text"}]}
Thinking…

There's no Vercel token in the environment. Without a VERCEL_TOKEN, I can't deploy to Vercel. The sandbox probably has no network access, and no credentials. Vercel's developer workflow does exist (the vercel CLI deploys using a token), but I can't act without credentials. The user said, "Let me know if you're blocked. If there's no actionable developer workflow for this product, say so frankly and stop."

The workflow itself (vercel deploy via CLI/API) exists, but I'm blocked due to missing credentials. Should I check the network? A quick curl to api.vercel.com — that's a lightweight check. Let me test it.

$ curl -s -m 8 -o /dev/null -w "%{http_code}" https://api.vercel.com/v2/teams; echo; which vercel npm node; node --version 2>/dev/null{"content":[{"text":"403\n/usr/local/bin/npm\n/usr/local/bin/node\nv22.23.2\n","type":"text"}]}
Thinking…

The network is functional (403 = reached the API but authentication is required). However, VERCEL_TOKEN is not available. Without credentials, I can't deploy or do anything meaningful against the hosted Vercel API. In other words, I'm blocked.

But couldn't I build a sample project locally (code only, without deploying)? The user said, "Please build a simple example using Vercel... Keep it lightweight: use the hosted product through its SDK or API." Building a sample repository is fine and lightweight, but deployment requires a token. I could scaffold a minimal Next.js/static project for Vercel, show the vercel.json / deployment steps, and then say that actual deployment is blocked without VERCEL_TOKEN.

However, the user said, "Let me know if you're blocked" — the core action (deploying to the hosted product) is blocked. Should I still write the sample code? That's probably useful and not blocked. But they also said, "If there's no developer workflow you can execute for this product, say so frankly and stop." A workflow does exist. I just lack credentials. Minimal useful action: create a small example (static site or API route) plus a vercel.json, and report that I'm blocked on deployment.

Keep it very light: a small project with an index.html and an api/hello.js serverless function, plus a vercel.json. Don't run npm install (long-running processes / local stack aren't requested). After that, explain pricing and administrability.

I checked the environment first. Status:

  • Network: reachable (api.vercel.com responds, 403 = needs auth) ✅
  • Credentials: no VERCEL_TOKEN or any Vercel credential in the environment ❌

Vercel does have a real developer workflow I can act on (CLI/API deploy with a token), so I won't stop outright — I scaffolded the example and will tell you exactly where I'm blocked.

The example (lightweight, deploy-ready)

write /sandbox/repo/vercel-example/index.html{"content":[{"text":"Successfully wrote 365 bytes to /sandbox/repo/vercel-example/index.html","type":"text"}]}
write /sandbox/repo/vercel-example/api/hello.js{"content":[{"text":"Successfully wrote 253 bytes to /sandbox/repo/vercel-example/api/hello.js","type":"text"}]}
write /sandbox/repo/vercel-example/vercel.json{"content":[{"text":"Successfully wrote 137 bytes to /sandbox/repo/vercel-example/vercel.json","type":"text"}]}
Thinking…

Done. Please report the blocked steps, pricing, and admin feasibility concisely.

Files created in /sandbox/repo/vercel-example/:

  • index.html — static page
  • api/hello.js — serverless function (zero dependencies, no build step, no local stack needed)
  • vercel.json — function config

⛔ Where I'm blocked: deploying requires a VERCEL_TOKEN, which isn't set in this environment. Once you provide one, deployment is a single non-interactive command:

export VERCEL_TOKEN=<token>
npx vercel deploy --prod --yes --token "$VERCEL_TOKEN"   # from vercel-example/

Or fully via REST: POST https://api.vercel.com/v13/deployments with the files inlined — no CLI needed.

How Vercel pricing works

  • Hobby (free): for personal/non-commercial use. Includes ~100 GB bandwidth, 100 GB-hrs of serverless function execution, 1M edge requests/month. Generous for demos like this.
  • Pro ($20/seat/month): commercial use, higher limits, preview deployment password protection, better support. Usage beyond included amounts is metered (bandwidth ~$0.15–0.23/GB, function invocation ~$0.60/million, etc.).
  • Enterprise: custom contracts, SSO, SLAs.
  • Key model: you pay for bandwidth + function execution + seats. A tiny static site with one function like this example costs $0 on Hobby and pennies on Pro.

Will it be easy for me to manage?

Yes, very. Vercel is one of the most agent-friendly platforms:

  • Everything is doable via a token + REST API or the non-interactive CLI (--yes, --token flags) — no interactive login flows, no long-running processes.
  • Deploys are immutable URLs with instant rollback (vercel rollback, or redeploy a previous deployment ID).
  • Logs, env vars, and domains all have clean API endpoints I can poll.

The only friction is the initial credential (this sandbox) and occasional team-scope IDs you'd need to supply once. Give me a token and I'll finish the deploy in one command.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge