Kivo

SDKs

Thin clients around a simple review-run contract.

SDKs should make capture easy without hiding what matters: intended use, supplied sources, citations, and review-run IDs.

TypeScript

Use in Next.js, Node workers, support pipelines, and AI product backends.

Python

Use in eval jobs, notebook audits, and internal model review harnesses.

REST-first

Every SDK maps to public REST endpoints so teams can inspect or replace the wrapper.

Example client call

Capture should be explicit enough that source handling and intended use are visible during code review.

await kivo.reviewRuns.create({
  intendedUse: "customer_facing",
  output,
  sources,
  metadata: {
    workflow: "support_answer"
  }
});