Skip to main content
ALTCHA®

Use cases

Each use case describes what you're defending against, the security-group presets and rules to start from, the frontend and backend code that deploys them, and what to watch once it runs. Pick the one closest to what you protect; most sites combine several.

Use caseProtectsEntry pointStarting configuration
User registrationSign-up formsWidget, then POST /v2/verify/signatureStrict + Form fields (consumer sign-ups)
Login & authenticationLogin formsWidget, then POST /v2/verify/signature and POST /v2/classifierStrict
Contact & lead formsContact, quote and newsletter formsWidget, then POST /v2/verify/signatureRecommended + Form fields
Chat & forum moderationMessages, comments and postsPOST /v2/classifier from your backendBackend API (allowed IPs) + similarity groups
Backend & API protectionYour APIs, and Sentinel's backend keysPOST /v2/classifier, POST /v2/threatBackend API (allowed IPs)
Inbound email screeningSupport inboxes and ticket systemsPOST /v2/emlBackend API (allowed IPs)
Threat detectionEvery widget key and backend checkThreat lists, POST /v2/threat, POST /v2/threat/_reportRecommended + Block AI agents

Every widget flow uses a public key for the widget and a restricted key for your backend, whose group uses the Backend API (allowed IPs) preset in every use case. See API keys & access levels and Security presets.

Start typing to search...

↑ ↓ Navigate ↵ Select