Build on Kiket with the API, SDKs, CLI, and MCP — cases, evidence, findings, and automation.

Developer

Developers use Kiket to integrate operational evidence, automate compliance checks, and build custom workflows on top of the platform API.

What you can build

Capability	Use case
REST API	Create cases, link evidence, run scans, manage findings
Webhooks	React to `case.created`, `finding.opened`, `scan.completed`
SDKs	TypeScript, Python, Go, Java, .NET clients
CLI	Script scans, exports, and workspace operations
MCP	Give AI agents structured access to cases and findings

Quick start

# Install CLI
npm install -g @kiket/cli

# Authenticate
kiket auth login

# List cases in a workspace
kiket cases list --workspace acme-corp

# Run a compliance scan
kiket scan run --framework soc2

API authentication

Create scoped keys under Settings → API Keys in the web app, or use OAuth for user-delegated access:

curl -H "Authorization: Bearer $KIKET_API_KEY" \
  https://api.kiket.io/v1/workspaces/acme-corp/cases

See API overview for scopes and rate limits.

SDK example

import { KiketClient } from '@kiket/sdk';

const client = new KiketClient({ apiKey: process.env.KIKET_API_KEY });

const cases = await client.cases.list({ workspaceId: 'acme-corp' });
const findings = await client.findings.list({ severity: 'high' });

Webhook integration

// Express handler for Kiket webhooks
app.post('/webhooks/kiket', (req, res) => {
  const { event, data } = req.body;

  switch (event) {
    case 'finding.opened':
      notifySlack(`New finding: ${data.title}`);
      break;
    case 'scan.completed':
      updateDashboard(data.scanId, data.summary);
      break;
  }

  res.status(200).send('OK');
});

MCP for AI agents

Configure the Kiket MCP server so Cursor or Claude can query cases and findings:

{
  "mcpServers": {
    "kiket": {
      "command": "npx",
      "args": ["-y", "@kiket/mcp-server"],
      "env": { "KIKET_API_KEY": "your-key" }
    }
  }
}

See MCP server for available tools.

Common patterns

CI/CD gate

Block deploys when critical findings are open:

- name: Kiket compliance gate
  run: |
    FINDINGS=$(kiket findings list --severity critical --status open --json)
    if [ "$(echo $FINDINGS | jq length)" -gt 0 ]; then
      echo "Critical findings block deploy"
      exit 1
    fi

Evidence ingestion

Push custom evidence via webhook or API:

curl -X POST https://api.kiket.io/v1/events \
  -H "Authorization: Bearer $KIKET_API_KEY" \
  -d '{"source":"ci","type":"deployment","workspaceId":"acme-corp"}'

Resources

API reference
CLI commands
SDK packages
Webhook events
Operational loop — how cases, evidence, and findings connect

Developer

On this page