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 case | Protects | Entry point | Starting configuration |
|---|---|---|---|
| User registration | Sign-up forms | Widget, then POST /v2/verify/signature | Strict + Form fields (consumer sign-ups) |
| Login & authentication | Login forms | Widget, then POST /v2/verify/signature and POST /v2/classifier | Strict |
| Contact & lead forms | Contact, quote and newsletter forms | Widget, then POST /v2/verify/signature | Recommended + Form fields |
| Chat & forum moderation | Messages, comments and posts | POST /v2/classifier from your backend | Backend API (allowed IPs) + similarity groups |
| Backend & API protection | Your APIs, and Sentinel's backend keys | POST /v2/classifier, POST /v2/threat | Backend API (allowed IPs) |
| Inbound email screening | Support inboxes and ticket systems | POST /v2/eml | Backend API (allowed IPs) |
| Threat detection | Every widget key and backend check | Threat lists, POST /v2/threat, POST /v2/threat/_report | Recommended + 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.