Standard v3 (proxyless)
"recap_v3"Use this for most pages when you only need a valid token. Captcha.fun runs the solve on our infrastructure, with no proxy required.
recap_v3.json
reCAPTCHA v3 Solver API
Solve standard and Enterprise reCAPTCHA v3 with a simple REST API. Ready tokens in under 3 seconds.
reCAPTCHA v3 Demo
Privacy - Terms
reCAPTCHA v3 pricing
| Product | Proxyless kind | Proxy kind | Speed | Price per 1k |
|---|---|---|---|---|
| reCAPTCHA v3 | "recap_v3" | "recap_v3_proxy" | <3s | $1.00 / 1k |
| reCAPTCHA v3 Enterprise | "recap_v3_enterprise" | "recap_v3_enterprise_proxy" | <3s | $2.50 / 1k |
What is Google reCAPTCHA v3?
Google reCAPTCHA v3 is an invisible risk check that runs in the background while a visitor uses a site. Instead of showing a checkbox or image puzzle, the page script evaluates behavior around a specific action, such as login, signup, checkout, or a form submit, and returns a trust score from 0.0 to 1.0. Higher scores are more likely to represent normal human traffic, while lower scores are more suspicious. Site owners choose their own threshold and decide whether low scoring traffic should be challenged, reviewed, rate limited, or blocked.
How to solve reCAPTCHA v3 with Captcha.fun
Pick a solve kind, send it in the request body, then follow the API steps below. All modes use the same endpoints; only the kind field and optional proxy change.
Product
Routing
| Field | Required | Purpose |
|---|---|---|
| kind | Yes | Select standard, Enterprise, proxyless, or proxy-backed v3 solving. |
| url | Yes | The page URL where the reCAPTCHA v3 token will be used. |
| siteKey | Yes | The public site key from the target page. |
| action | When used | The page action, such as login, signup, checkout, or submit. |
| proxy | Proxy kinds only | Your proxy string when IP, geo, or session continuity matters. |
Step 1: Create request
POST /v1/request
Send your API key in the API_KEY header and pass "recap_v3" in the JSON body.
create-recap_v3.sh
Response
Response
200 OK
Step 2: Get response
GET /v2/response/{id}
Poll with the id from step 1 about once per second until ready is true. Most v3 solves finish in a few seconds. Use token as the solved reCAPTCHA value, and reuse userAgent and secUa when your submit flow depends on browser context.
poll.sh
Response
Response
200 OK
reCAPTCHA v3 solver FAQ
Practical details that matter before you wire the token into a production submit flow.
Does reCAPTCHA v3 show a checkbox?
No. reCAPTCHA v3 usually runs in the background and returns a score-based token for an action such as login, signup, checkout, or form submit.
Do I need to send the action field?
Send action when the target page uses one. The action should match the page workflow because many sites verify that the returned token was created for the expected action.
When should I use a proxy kind?
Use a proxy kind when the token request needs to match your browser session, geography, or network path. If network path does not matter, start with proxyless.
How often should I poll for the response?
Create the request, keep the returned id, then poll the response endpoint about once per second until ready is true.
Ready to integrate reCAPTCHA v3 solving?
Create an account, add credits, and use the request and response endpoints from the docs to start testing standard or Enterprise v3.