Events Rules Overview API & Integration

Traffic Intelligence

Monitor traffic, threats, and assessment activity across your application

Total Evaluations

—

Threats Detected

—

Threat Rate

Device Flags ?

—

Traffic Overview

Monitor traffic distribution and threat composition across the selected range

Daily evaluations

Last 14 days

Clean

Threat

Signal composition

Outcomes, network intelligence, and the device layer side by side

Identification events

Every evaluation your API key ran — select a row for the full network + device picture. The same data is available by server API.

—

Evaluations · all time

—

Threats flagged

—

VPN / proxy exits

—

Events today

Time	Visitor	IP address	Client	Signals	Decision

Decision rules

Your policy, applied on the API itself: when a signal fires, the decision field returns the action you chose — your backend just routes on it. The engine's own verdict stays in engine_decision. If several rules match, the most severe wins.

Who does the blocking? Your code does — Sentinel decides, you enforce. Sentinel never sits between your users and your site. Your page collects the signals, your backend sends them to POST /v1/evaluate, and the response's decision carries the action you configured below. Enforcement is one branch in your handler — and because these rules run on the API, you can tighten or loosen policy here without redeploying anything:

Your backend

const r = await sentinel.evaluate({ token, fingerprintEventId });

if (r.decision === 'block')  return res.status(403).json({ error: 'Not allowed' });
if (r.decision === 'review') await queueForManualReview(user, r);   // your flow
// 'allow' — continue as normal

Signal actions

"Engine default" leaves the risk-score verdict untouched for that signal

Exceptions

Pin one IP address or visitor to always allow or always block — pins outrank the signal actions above

Loading…

Verify a rule in one line — test tokens obey your rules, so after saving "VPN → Block" this returns "decision": "block":

cURL

curl -X POST https://sntlhq.com/v1/evaluate \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"token":"test_vpn"}'

— —

—risk score

Identification

Visitor ID—

Events from this visitor—

First seen—

Last seen—

Location & network Spur network intelligence

IP address—

Country—

Service—

Device Fingerprint device intelligence

Browser—

Operating system—

No device layer on this event — pass fingerprintEventId from the client SDK to unlock browser, OS, antidetect and bot signals. See how →

Actions

Allow/block pins apply from your next evaluation and outrank signal rules. Manage them in the Rules tab.

Event record

API & Integration

Everything you need to wire Sentinel into your stack — credentials, endpoint, and a live playground

Credentials & Endpoint

Authenticate from your backend and POST visitor tokens for evaluation

API Key

Authorization: Bearer sk_live_… · 1,000 req/hr free tier

Docs ↗

                    Keep this key secret — it authenticates all API calls. Rotate if compromised.
                

Endpoint

POST from your backend

loading…

Node.js — backend example

const result = await fetch('…/v1/evaluate', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer sk_live_YOUR_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ token: req.body.sentinelToken })
});
const data = await result.json();
// data.decision → 'allow' | 'review' | 'block' — route on this

Test & Ship

Deterministic test tokens, a public sandbox key for CI, and the official SDKs

CI & Sandbox

No key required — safe for pipelines and staging

The public sk_test_sandbox key answers the deterministic test_* tokens with the documented response shapes. Never billed, never stored, never counts against your quota.

cURL — works from any CI runner

curl -X POST https://sntlhq.com/v1/evaluate \
  -H "Authorization: Bearer sk_test_sandbox" \
  -H "Content-Type: application/json" \
  -d '{"token":"test_vpn"}'

Tokens: test_clean · test_vpn · test_proxy · test_datacenter · test_tor — with your live key they exercise the same paths, still unbilled. Sandbox docs →

SDKs & Resources

Official packages and machine-readable specs

Node.jsnpm install @sentinelsup/sdknpm ↗

Pythonpip install sentinelsupPyPI ↗

API reference OpenAPI 3.1 AI-agent guide Webhook alerts Signal glossary

Playground

Run your first evaluation against the live API

Loading SDK…

Waiting for the security token…

Simulate a verdict — deterministic test tokens, never stored or billed

Sentinel Network · 24h — evals — threats 0 VPN 0 Proxy 0 DCH Network-wide

Tools

Traffic Overview

Devices & Services

Geo Intelligence

Time of Day

Identification events

Decision rules

Credentials & Endpoint

Test & Ship