1
Create a challenge
Request a challenge token from the API.
Built for teams that need better signal than static puzzles.
How it works
How it works
2
Verify behavior
Collect gameplay telemetry and submit it to the verification endpoint.
3
Make a decision
Use structured response fields to allow, review, step up, or block traffic.
API
Two endpoints. One verification flow.
POST /challenge
Create a new verification session.
Issue a token before rendering a challenge in the client.
POST /verify
Submit challenge telemetry and receive a decision.
Send gameplay data and evaluate the structured response in real time.
Sample response
Structured output for real-time decisions
Verification response
JSON
{
"decision": "Human",
"human_probability": 0.94,
"confidence": 0.88,
"reason": "scored_by_dca_package_stack",
"runtime_path": "scorer-path",
"engine_class": "scorer",
"evidence": {
"quality": "high",
"samples": 240,
"successEvents": 8,
"model_features_used": 133
},
"risk_flags": []
}
Why teams use it
Why teams use it
Behavior, not static puzzles
Evaluate how a user interacts, not just whether they clicked the right image.
Structured output
Get machine-readable decisions, confidence, evidence, and risk signals.
Fits modern risk pipelines
Use it for signup abuse, login defense, scraping resistance, and high-risk actions.
Use cases
Use cases
- Account creation
- Login protection
- Password reset
- Promo and gift card abuse
- Scraping and automation defense
- High-risk workflow step-up