Documentation
Ship the integration first. Then go deeper.
This is the docs entrypoint for Playtcha. Start with the quickstart if you want a working integration in under five minutes. Then use the migration, framework, and security guides to harden the edges.
Start here
These pages are live now and cover the most common implementation paths.
Quickstart
The 5-minute path: mount the widget, verify on your server, and test the flow end to end.
Open guide →Next.js on Vercel
Server Actions, Route Handlers, env vars, and failure-mode choices for Vercel-hosted apps.
Open guide →React + Vite
Mount the widget in a client-rendered app, keep the token in your submit path, and verify on your backend.
Open guide →Supabase Auth
Protect Supabase Auth signups with verify-before-signUp and a cleaner rollout shape for auth-heavy teams.
Open guide →Migrate from reCAPTCHA
Replace reCAPTCHA without breaking signup, contact, or checkout flows.
Open guide →Server verify for Node
Minimal and production-ready examples for calling /v1/verify from Node 18+.
Open guide →Token lifecycle
Challenge token, result token, single-use redemption, and where origin/session binding actually happens.
Open guide →Looking for a specific route?
Use cases and comparisons still matter, but they do not need their own giant sections here.
Domain whitelist reference · Verify from Node · Verify from Python · Verify from PHP · Verify from Go · Verify from Ruby
Signup forms · Login forms · Contact forms
React apps · Next.js apps · Single-page apps
Mobile web apps · In-app signup · WebView auth
reCAPTCHA vs Playtcha · reCAPTCHA Enterprise vs Playtcha · Invisible CAPTCHA vs Playtcha · Migration guide
Next up
A short queue, not a content wall.
Verify API reference
Split the verify request and response contract into one formal API reference page instead of repeating it in every language example.
