Rubi developer documentation
Everything your engineers need to put AI interviews inside your risk workflow: a REST API, signed webhooks and data connectors for Axcera or your own platform.
QuickstartCreate an API key and send your first interview with curl.Interviews APICreate, list, read reports, record decisions, stream media.WebhooksSigned events for every step, with Node and Python verification.Custom API specThe five read only endpoints your platform exposes to Rubi.
Base URL#
All API requests go to https://api.rubikyt.com over HTTPS. JSON is snake_case and every timestamp is an RFC 3339 string in UTC.
bash
curl https://api.rubikyt.com/v1/interviews \
-H "Authorization: Bearer $RUBI_API_KEY"Surfaces#
| Surface | Prefix | Credential |
|---|---|---|
| Public API and dashboard | /v1/* | API key rubi_live_... with scoped permissions |
| Trader interview | /t/* | Invite token from the link interview.rubikyt.com/i/{token} |
| Shared report | /r/{token} | The token in the path, read only, expiring |
| Public | /public/* | None, rate limited per IP |
As an integrator you only use /v1. The trader and share surfaces are driven by links Rubi generates for you.
Core concepts#
- Interview: one session for one trader, created with an invite link. Lifecycle
created,consented,in_progress,submitted,report_ready, orfailed. - Report: the AI assessment with a risk score, a recommended step and three concern verdicts (third party, cross account, gamification).
- Decision: your analyst's call,
approved,rejectedorneeds_review, independent of the status. - Trader: a CRM record with accounts, trades and payouts, created by you or synced from an integration.
Sandbox#
Pass "sandbox": true when creating an interview to run a short test session that does not count against your plan. Use it to rehearse your webhook handling end to end.