Documentation

Kairos documentation

Kairos is a decision engine. You send it what happens in your product, you say in plain language what you want decided, and at the moment of action you ask. It answers with approve, step up, review or block, and with the signals behind the answer.

Get started

Get started › OverviewWhat Kairos does, how a decision is made, and what it does not do.QuickstartMake an account and a key, define an action, and get a first decision.Import your historyLoad your transactions, customers and chargebacks, so the first decisions have something to read.

Platform

AuthenticationSecret and public API keys, signed-in sessions, key limits, rotation, and the errors.EnvironmentsProduction and sandboxes: what is separate, how to copy data, and how to move a change to production.WorkspacesAccounts, sign-in, workspaces, roles and invites.Webhooks › InboundLet a provider such as Stripe send its webhooks to Kairos, with no code.Webhooks › OutboundSigned messages to your system when a decision, a label or a case changes.DashboardsPages of tiles that you build, and what a tile can ask.WorkflowsWork that Kairos does after an event, a change, a schedule or a call.ModelsQuestion models such as Grayson, and scoring models such as XGBoost that you train on your outcomes.The consoleThe web interface: the sidebar, the pages, and the settings.

Concepts

Core conceptsEntities, events, records, sessions, labels, links, actions, policies, models and decisions.EventsWhat happened: the shape of an event, how to send it, records that change, and sessions.EntitiesUsers, devices, payees and the rest: how to name them, set their properties and define their types.ActionsA decision you want made, in plain language: the question, signals, typologies, policy and totals.DecisionsAsk at the moment of action, read the answer, see why, resolve it, and test on the past.LinksWhat a decision is told about the other subjects that share a device, an account or a payee.

Case management

QueuesWhich decisions open a case, how cases are grouped, and when a case is due.CasesWhat a case holds, and how to assign, resolve and reopen it.LayoutsA layout for the cases of each queue, made in the editor.

Templates

Templates › OverviewAction definitions, event shapes and webhooks to copy and change.Event templatesRecommended shapes for common events, one page each.

Reference

API referenceEvery HTTP endpoint, its request and its response.MCPConnect Cursor, Claude Code and other agents to Kairos through the Model Context Protocol.Clients › TypeScript SDK@finic-ai/kairos: record what happens, say what you want decided, and ask at the moment of action.Clients › Python SDKfinic-kairos: the same client, with Python names.Clients › JavaScriptkairos.js: the device of each visitor, the pages of your client settings, and events of your own.Clients › Edge@finic-ai/kairos-edge: the routes of your client settings on Cloudflare, Fastly or CloudFront, with no change to your app.Clients › CLIkairos: events, imports, decisions, cases and models from a terminal.

Deployment

Self-hostingRun Kairos on your own infrastructure: Docker, Postgres, migrations, upgrades, backups and security.ConfigurationEvery environment variable of a self-hosted server.Sign-in and accessWho can sign up on your server, Supabase and OAuth, and how credentials are kept.