Skip to main content
ALTCHA®

Features

Sentinel combines several independent detection mechanisms into one decision. This page shows where each one acts, what turns it on, and which endpoint exposes it, so you can pick the pages that matter for your integration.

Where each feature acts

A widget submission passes three stages. Each feature acts in one or more of them.

  1. Before the challenge. The API key's security group evaluates its rules against the request. Rules can deny it based on threat intelligence (threat, threatVerdict), the agent that signed it (agent), the client's penalty or risk, its country, network, and headers. Matching set rules choose the settings for the next two stages, and rate limits and header entropy are counted.
  2. The challenge. GET /v2/challenge issues a proof-of-work challenge with the algorithm and cost the rules chose. Rules can add a code challenge or turn on Human Interaction Signature, which scores how the user interacted with the page before the challenge is issued.
  3. The submission. POST /v2/verify checks the solution, then the classifier scores the request and the form fields the widget sends: spam, profanity, and injection in the text, phishing URLs, similarity to your training data, and, when a group opts in, the AI decider. The verdict is signed into verificationData for your backend. See Verifying submissions.

Your backend can also call most detection features directly, without a widget, with a restricted or full API key. See Backend detection APIs.

Feature map

FeatureActs inTurned on byDirect API
Proof-of-workChallengeAlways on; pow.* set fields tune itGET /v2/challenge
Code challengeChallengecodeChallenge.enabled set field—
Human Interaction SignatureChallengehis.mode set fieldPOST /v2/challenge
Rate limiting & penaltyEvery request[rate_limit] (global, on by default); rateLimit.*, headerEntropy.*, penalty.add set fields—
ClassifierSubmissionAlways on in POST /v2/verify; classifier.* set fields tune itPOST /v2/classifier
Spam, profanity & injectionSubmissionClassifier text and injection categories, when text is sentPOST /v2/classifier
Similarity & training dataSubmissionCampaign detection on by default; training data in the account; [similarity] provider for semantic matchingPOST /v2/similarity
AI deciderSubmission[classifier.ai] provider plus classifier.ai set field— (runs inside the classifier)
Threat intelligenceEvery request, submission, admin loginsThreat sources and entries; threat rule conditions; [auth] block_threats (on by default) for loginsPOST /v2/threat
Phishing detectionSubmission[classifier.phishing] listPOST /v2/phishing
Email analysis (EML)Backend only[eml]POST /v2/eml
Bots & AI agentsBefore the challenge[web_bot_auth]; agent rule condition—
Lookups & inspectDebugging, enrichment[ip_resolver]; [inspect]POST /v2/ip, /v2/language, /v2/user-agent, /v2/time-zone; GET /v2/inspect

Credential types differ by endpoint: widget endpoints take a public key, detection endpoints a restricted or full key. See API keys & access levels.

What a new security group does

A security group without rules still protects a widget:

  • Every challenge is proof-of-work with PBKDF2/SHA-256 at cost 5000.
  • POST /v2/verify classifies the request (and the form fields, when the widget sends them) and signs the verdict.
  • The global per-IP rate limit, [rate_limit] global (default 100/1m), applies.
  • The code challenge, Human Interaction Signature, rule rate limits, header entropy, and the AI decider are off.

To turn the rest on without writing rules by hand, apply the Recommended preset in the admin UI. It blocks IPs with a threat verdict of block, rate-limits each device, limits header entropy, and gives clients with high risk or penalty a code challenge and a harder proof-of-work. See Security presets.

Where to start

In this section

  • Proof-of-work: Sentinel's proof-of-work algorithms, including memory-hard Argon2id and scrypt, and how security-group rules set their cost.
  • Code challenge: An image or audio code that security-group rules can require for suspicious requests, and its accessibility features.
  • Human Interaction Signature: How Human Interaction Signature (HIS) scores interaction signals, its modes, replay detection, and its limitations.
  • Rate limiting & penalty: Global and per-rule rate limits, Ephemeral Device Keys, header entropy checks, and the penalty score.
  • Classifier: How the classifier scores a submission across email, device, IP, location, text, similarity, and other categories into a verdict.
  • Spam, profanity & injection detection: Sentinel's deterministic multilingual spam filter, profanity detection, and injection rules for submitted text.
  • Similarity & training data: Match submissions against your labeled training data, detect near-duplicates and campaigns, and manage training suggestions.
  • AI decider: Let an AI model review submissions during classification: providers, per-group settings, data sent, and failure behavior.
  • Threat intelligence: Block or allow IPs from threat sources and from manual or automatic entries, and use threat data in rules and the classifier.
  • Phishing detection: Detect known phishing URLs in submitted text and check URLs with the phishing API.
  • Email analysis (EML): Analyze raw inbound email messages: authentication results, attachments, malicious hashes, and EML rules.
  • Bots & AI agents: Identify bots, crawlers, and AI agents with Web Bot Auth signatures, the agent rule condition, and presets, and control their access.
  • Lookups & inspect: Look up IP, language, user-agent, and time zone information, and inspect how Sentinel evaluates a request.

Start typing to search...

↑ ↓ Navigate ↵ Select