Source boundary
Vercel
Confirm source eligibility in your workspace before creating access.
- Financial source
- Team billing charges and validated billing or usage records
- Reviewed
- 2026-09-17
- Cost bases
- net, billed, list, contracted, credits
- Useful dimensions
- team, project when supplied, charge type, usage period
Known limits
- Project, region, and resource identities may be absent.
- Usage and invoice cost remain distinct when the source does not reconcile them.
Prepare the connection
Eligibility
The selected team must expose billing usage to the credential's team scope; provider plan and role restrictions still apply.
Authorize billing access through Vercel, or provide a scoped team token. OAuth tokens are encrypted and never displayed.
Authentication choices
- Vercel authorization — recommendedPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
- Team access tokenPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
Connection details
| Field | Why it is needed | Example format |
|---|---|---|
| Team ID | Team whose billing usage will be read. | team_… |
Permission boundary
| Resource | Read or bounded staging permissions | Purpose |
|---|---|---|
| Selected Vercel team | billing and usage read | Read team usage and cost without deployment, project, domain, secret, or payment mutation. |
Connection sequence
- Confirm the team plan and role can view detailed usage.
- Create a dedicated token scoped to that team.
- Enter the team ID and token.
- Validate the team identity, reporting eligibility, pagination, and supported date range.
Validation and first sync
Validation rejects a personal or different-team scope, missing billing visibility, unsupported plan, incomplete pagination, or mutation-capable operation.
The first sync reads a bounded date range and keeps billed/effective cost distinct from raw usage quantities.
Freshness: Current-period usage can remain provisional until billing settles.
Remove access
Revoke the PruneFox connection and delete or revoke the dedicated token or OAuth grant.
Troubleshooting
Check team ID, token team scope, role, plan eligibility, reporting date range, and pagination.
Verify the first completed period
Compare one bounded completed period with the provider billing source. Match currency and cost basis, inspect credits and adjustments, and confirm that missing dimensions remain unavailable rather than zero.
Troubleshoot safely
Use the visible connection state, provider name, affected date range, and expected outcome. Never send credentials, raw billing exports, payment data, or customer records through support.