VercelToken
Pass the Vercel Security Checkpoint through your own proxy and get the _vcrcs cookie for the protected site. With the schema, an example and provider prices.
VercelToken passes the Vercel Security Checkpoint for a URL through your proxy and returns the _vcrcs cookie value. The Vercel Firewall can show this checkpoint to check that the request comes from a real browser with JavaScript, and sets the _vcrcs cookie on the site once the check passes.
Recognize the checkpoint
Request the protected site. The response is a checkpoint page instead of the content, and the browser completes the check by calling a path under /.well-known/vercel/security/. Send the URL you were blocked on as websiteURL.
Use your proxy
task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Replay the cookie from the same address. Optionally send userAgent, and use the same User-Agent for your own requests.
Use the cookie
Set solution._vcrcs as the _vcrcs cookie on the protected site and retry the request. If the checkpoint appears again, check that the proxy kept one IP for the whole solve and that you retry from that address.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
RiskBypass | $1.00 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes. View settings reference |
Task Object Properties
The task field accepts an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the page where the CAPTCHA is displayed. Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
userAgent | string | No | Browser User-Agent string. Must match the browser used on the target page. Not all providers properly support this parameter. Verify the compatibility with the provider you are using. Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "VercelToken",
"websiteURL": "https://example.com/",
"proxy": "http://user:pass@1.2.3.4:8080"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
_vcrcs* | string | Yes | Value of the Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |