Two calls
The whole integration rests on two endpoints.Ask for a decision
Send an event, get the outcome and its reasoning in the same response.
Send data
Send events separately to store them and feed velocity rules.
How a decision comes together
1
An event arrives
A payment, a login attempt or a signup — in your own data model, with your own field names.
2
Signals are derived
Email, phone, IP and device signals are read from lists held inside your
infrastructure. Nothing is queried outside.
3
Rules run
The scenario’s rules are evaluated and each one that fires adds its score.
4
An outcome returns
Thresholds turn the total into an outcome, and the contribution of every rule comes
back in the response.
When it is the right tool
Krino earns its place when a decision has to be explainable and the rules change often. If you have to answer a customer asking why they were declined, or an auditor asking what a decision rested on, you end up with more than a score.Krino is not a machine-learning scoring service. You define the decision; the product
applies it quickly, consistently and traceably.
What’s next
Quickstart
Get your first decision in fifteen minutes.
Concepts
Scenario, version, rule, threshold, case — what each one means.