Migrating from NopeCHA

Solvecha follows the request and response formats, the error codes and the endpoint paths of the NopeCHA recognition API. For most clients the switch is two changes.

- BASE = "https://api.nopecha.com"
- KEY = "YOUR_NOPECHA_KEY"
+ BASE = "https://api.solvecha.com"
+ KEY = "YOUR_API_KEY"

#What stays the same

#Differences to know

• Request bodies. JSON and url-encoded form bodies work. Multipart does not.
• Plan. A key needs an active plan to solve. Without a plan the API answers error 16.
• Quota window. The daily quota resets at 00:00 UTC. NopeCHA uses a rolling 24 hour window. GET /v1/status shows lastreset, ttl and duration for the UTC day.
• Types. Solvecha supports the five recognition types on the captcha types pages. Other NopeCHA products are not offered.
• Fallback. When our own models cannot answer a request, the engine passes the image and the task text to NopeCHA and returns its answer. The Privacy Policy describes this.
• Browser extension. If you use a browser extension, use the Solvecha extension. It solves reCAPTCHA v2 image challenges.

#Test the switch

Call the status endpoint with your new key. It costs no quota.

curl "https://api.solvecha.com/v1/status" -H "Authorization: Bearer YOUR_API_KEY"

Then send one real job with your usual code. Check the quota with GET /v1/status afterwards: it drops by one for each answer you fetched.

For prices side by side, with sources, see the compare page.