Vercel Connect Pricing
Vercel Connect is billed by token requests and triggers.
A token request is a single call to the Vercel Connect API that returns a provider token, for example a getToken call from your application or agent.
A trigger is an incoming webhook from a third-party service that Vercel Connect verifies and forwards to a trigger destination (a linked project).
| Plan | Token request pricing |
|---|---|
| Hobby | 500 token requests per month included at no extra charge |
| Pro | $3.00 per 1,000 token requests |
| Enterprise | Custom |
In-process token caching reduces token requests significantly. The SDK reuses a cached token across calls until it falls inside the validity buffer, so a typical agent that makes many provider calls in one invocation pays for one token request, not many.
| Plan | Trigger pricing |
|---|---|
| Hobby | 1,000 triggers per month included at no extra charge |
| Pro | $0.95 per 1,000 triggers |
| Enterprise | Custom |
Each trigger destination that receives the webhook event counts as one trigger. For example, a webhook event forwarded to three trigger destinations counts as three triggers. If no trigger destinations are configured, each incoming webhook event still counts as one trigger.
Triggers are only counted for connectors that support trigger forwarding. If your connector does not use triggers, you are not billed for them.
To stop being billed for Vercel Connect:
- Token requests: Stop calling
getTokenfrom your application, remove the connector from any linked projects, and revoke or delete existing provider tokens from the connector's settings page - Triggers: Remove the webhook URL from the provider's dashboard so their webhook client stops sending events to Vercel Connect. Removing trigger destinations alone does not stop billing, because incoming webhook events still count as one trigger even without a configured destination
For platform limits and API rate limits, see Limits.
Was this helpful?