How Titan Works

Most Titan products share the same integration model — implement it once, and it carries across Bot Manager, Device ID, Phishing Protection, Email Intelligence, and Agent Trust Manager.

The core flow

For client-integrated products

Client — An Arkose script or mobile SDK runs in your app and collects signals, producing a session token.
Server — Your backend sends that token to an Arkose Verify endpoint.
Decision — Arkose returns a risk decision and supporting signals, which your backend acts on (allow, block, step up).

Please Note: Edge and Scraping Protection integrate differently — Edge is a server-side API you call with request signals, and Scraping Protection runs as a worker on your CDN. See their product sections for details.

Shared building blocks

Keys — Public and private keys identify your integration.
Session token — The artifact passed from client to server for verification.
Command Center — The console for monitoring and configuration across products.
Risk signals — A common signal set surfaced through the APIs and platform services.

Next step

Ready to integrate? See Setting up the Titan Products.