Captchas.ir / architecture
Each stage has a clear boundary
Understand the architecture before integrating
01 / IntentYour site request
02 / ChallengeBrowser challenge
03 / SiteverifyServer verification
04 / ConsumeOne-use consumption
Captchas.ir
A bound request, a verified decision
This is an architecture illustration See actual results in the CAPTCHA demo
Browser
The browser receives a public site key and challenge Verification credentials never belong in the interface
Go control plane
Requests bind to tenant, site, action, intent and configuration version Engine and instance stay pinned after issuance
Engine and verification
External engines keep isolated runtimes A timeout after verification dispatch can be indeterminate and is not treated as success
Consume and audit
Final consumption must be atomic Policy changes must not rewrite an active session’s contract