Skip to Content
AnySolver logo
AnySolver
Token

PerimeterXTokenProxyLess

Get PerimeterX cookies for a site from its PerimeterX app ID alone, using the provider's standard task, with no proxy. With the schema, example and prices.

PerimeterXTokenProxyLess takes only the PerimeterX app ID of the site and returns PerimeterX cookies. You send no proxy, URL or block payload. EZ-Captcha maps it to its PerimeterX task, while PerimeterXInvisibleTokenProxyLess maps to its PxInvisibleCaptcha task.

Which PerimeterX task do I need?

What you haveTask
You see a block page with a Press & Hold button, and solve through your proxyPerimeterXHoldToken
You have the init.js URL and the app ID, and solve through your proxyPerimeterXInvisibleToken
You have only the app ID, and want the provider's invisible task, from the provider networkPerimeterXInvisibleTokenProxyLess
You have only the app ID, and want the provider's standard task, from the provider networkPerimeterXTokenProxyLess (this task)

Find pxAppId

The app ID is PX followed by letters and digits. Open the protected page with DevTools: it appears in the init.js request URL (for example /px/PXxxxxxxxx/init.js on first-party setups) and in window._pxAppId in the console.

Use the cookies

Set the cookies in solution.cookies on your session and request the protected endpoints. The solution has no userAgent. Because you send no proxy, the provider uses its own IP. If the site rejects the cookies from your session, use a task that takes your proxy: PerimeterXHoldToken for a Press & Hold block page, or PerimeterXInvisibleToken for the init.js flow.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
EZCaptcha
$2.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

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:

FieldTypeRequiredDescription
type*
Yes
pxAppId*
stringYes

PerimeterX app ID of the target site: PX followed by letters and digits. Find it in the init.js URL or in window._pxAppId.

Example: PXu6b0qd2S

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "PerimeterXTokenProxyLess",
        "pxAppId": "PXu6b0qd2S"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
cookies*
Record<string, unknown>Yes

PerimeterX cookies to set on the session, such as _px3. Replay them from the same IP and User-Agent.

Example: {"_px3":"a1b2..."}

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.