EverySolve CAPTCHA API

Castle API

Q: What does Castle return, and what should not be confused with it?

The Castle API returns a set of tokens in `tokens`. Its solution format is `tokens`. It returns a token set. Do not collapse that set into one token or infer a visual CAPTCHA from the product name.

EverySolve's Castle API returns a set of tokens for your challenge workflow. Send POST /api/v1/captcha with type set to castle and the inputs listed below.

Castle is a risk and device-intelligence flow in which the target supplies structured metadata rather than a visible image puzzle. It returns a token set. Do not collapse that set into one token or infer a visual CAPTCHA from the product name.

Start for free View the type catalog

Endpoint: POST /api/v1/captcha
Type: castle
Per 1,000 successful solutions: $0.97 per 1,000 successful solutions

Request parameters

Provide website_url, website_key, and metadata. Optional parameters are count, user_agent, and proxy.

Required parameters

website_urlwebsite_keymetadata

Optional parameters

countuser_agentproxy

castle.sh

curl -X POST https://api.everyinfra.com/api/v1/captcha \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"castle","website_url":"<website_url>","website_key":"<website_key>","metadata":"<metadata>"}'

How to recognize Castle

Castle is a risk and device-intelligence flow in which the target supplies structured metadata rather than a visible image puzzle.

What makes Castle different

It returns a token set. Do not collapse that set into one token or infer a visual CAPTCHA from the product name.

Where the Castle parameters come from

website_key and metadata must come from the same target integration; count, user_agent, and proxy are optional request context.

website_urlRequired: The exact page where this challenge appears, including the relevant path rather than only the site home page.
website_keyRequired: The public site or widget key copied from this exact target integration; it is not a secret key.
metadataRequired: The structured, public client metadata required by the target Castle flow.
countOptional: The requested number of results for this task, subject to the current catalog contract.
user_agentOptional: The browser user agent for this challenge session; keep it consistent when the returned result is bound to that session.
proxyOptional: The proxy for the solve session; when a result is network-bound, use the same exit for the subsequent target request.

What the API returns

The Castle API returns a set of tokens in tokens. Its solution format is tokens. Use the returned tokens together according to the target workflow's request contract.

Solution shape: tokens
Solution fields: tokens

How to use the Castle API

01Read GET /api/v1/captcha/types and select the castle entry.
02Send type: "castle" and the required parameters to POST /api/v1/captcha.
03Read a set of tokens from tokens.
04Use the returned tokens together according to the target workflow's request contract.

Billing and availability

EverySolve charges only when a solution is delivered successfully. Unsuccessful attempts are refunded automatically. Read available and the price fields from GET /api/v1/captcha/types at request time rather than treating them as static page content.

Castle integration questions

How can I identify Castle before choosing a type?

Castle is a risk and device-intelligence flow in which the target supplies structured metadata rather than a visible image puzzle. Use castle only after those signals match the target challenge.

Which target-page values belong in a Castle request?

website_key and metadata must come from the same target integration; count, user_agent, and proxy are optional request context. Provide website_url, website_key, and metadata. Optional parameters are count, user_agent, and proxy.

What does Castle return, and what should not be confused with it?

The Castle API returns a set of tokens in tokens. Its solution format is tokens. It returns a token set. Do not collapse that set into one token or infer a visual CAPTCHA from the product name.

Which external source explains the Castle integration?

Castle's first-party site describes the risk and device-intelligence product context. [Open the Castle reference](https://castle.io/). EverySolve-specific fields and live availability still come from the type catalog.