vercel
VercelOfficial CLI · vercel
- Reads
- visitors, pageviews, top paths, and (with Web Analytics) conversions.
- Locators
- Deployment URL or project name.
- Evidence for a linked target
- Vercel CLI result, deployment metadata, or Web Analytics for the project.
- Official docs
- https://vercel.com/docs/cli
Usage
Agent command: superdense reward docs connectors --connector vercel
# vercel — usage Use the official `vercel` CLI to confirm the deployment, then read Web Analytics for the project (visitors, pageviews). ```bash # Confirm the live deployment for a project vercel ls <project> # Inspect a specific deployment vercel inspect <deployment-url> ``` **Reward dimensions:** visitors, pageviews, top paths, conversions. **Locators:** deployment URL, project name.
Install
Agent command: superdense reward docs connectors --connector vercel --section install
Install the official **vercel** CLI and authenticate it for the account that owns the artifact. Use the vendor's official installation guide rather than a copy here, so steps stay current: - https://vercel.com/docs/cli#installing-vercel-cli Once installed and authenticated, the `usage` section shows how to read metrics.
Troubleshoot
Agent command: superdense reward docs connectors --connector vercel --section troubleshoot
If a `vercel` call fails, the fastest fix is usually re-auth or a version bump. Check, in order: 1. **Auth** — confirm you are logged in to the right account/scope. 2. **Version** — update vercel to the latest release. 3. **Permissions** — confirm the account can see the resource. For anything deeper, use the official troubleshooting docs: - https://vercel.com/docs/cli