# Karumi

> Karumi is an agentic product-demo platform. Its AI agent runs personalized, interactive
> product demonstrations in a live video call, 24/7 and in multiple languages, across
> landing pages, in-app surfaces and outbound email — then logs the transcript, analysis
> and next steps into the CRM. Karumi exposes two machine-readable surfaces: a read-only
> Public REST API over session, transcript, insight, target and analytics data, and a
> hosted MCP server that lets an MCP client operate the whole workspace.

Generated by API Evangelist on 2026-08-13 from https://www.karumi.ai/ and Karumi's own
published artifacts. Karumi does not serve an llms.txt of its own (/llms.txt returns 404).
This is a third-party profile; see https://apis.io/provider/karumi.

## APIs

- [Karumi Public API](https://api.karumi.ai/api/v1/docs): Read-only REST API. Base
  https://api.karumi.ai/api/v1. Authenticate with an organization API key in the
  `X-Api-Key` header. Nine GET operations across three tags — Sessions, Analytics,
  Targets. Unauthenticated calls return 401 `{"detail":"Missing X-Api-Key header"}`.
- [Karumi MCP Server](https://www.karumi.ai/mcp-documentation): Hosted remote MCP server.
  Reachable endpoint https://api.karumi.ai/mcp/. OAuth 2.0 authorization code with
  explicit user consent; a 401 carries an RFC 9728 `WWW-Authenticate: Bearer
  resource_metadata=...` challenge. 37 tools, 24 read-only and 13 write/destructive
  (the write tools require client confirmation). Note: the connector URL published on
  Karumi's documentation page, https://mcp.karumi.ai, does not resolve.

## Operations (Public API)

- `list_sessions_sessions_get` — GET /sessions. Filter by project_id, status,
  start_date, end_date; paginate with limit (1..500, default 100) and offset.
- `get_session_sessions__session_id__get` — GET /sessions/{session_id}. Session plus
  full transcript and recording URL.
- `get_session_insights_sessions__session_id__insights_get` — GET
  /sessions/{session_id}/insights. Derived insights with confidence and evidence.
- `download_session_recording_sessions__session_id__recording_get` — GET
  /sessions/{session_id}/recording.
- `list_meeting_events_sessions_meeting_events_get` — GET /sessions/meeting-events.
- `get_analytics_analytics_get` — GET /analytics. Aggregate engagement analytics.
- `get_analytics_timeline_analytics_timeline_get` — GET /analytics/timeline.
- `list_targets_targets_get` — GET /targets. Demo projects; called "agents" on the MCP
  surface.
- `get_target_targets__target_id__get` — GET /targets/{target_id}. Target with its
  journeys.

## Specs

- [OpenAPI 3.1.0](https://api.karumi.ai/api/v1/openapi.json): Karumi Public API, version
  1.0.0. Harvested to `openapi/karumi-public-api-openapi.json`.
- [OAuth protected-resource metadata](https://api.karumi.ai/.well-known/oauth-protected-resource):
  RFC 9728 document for the MCP endpoint; delegates authorization to a Supabase Auth
  authorization server.

## Docs

- [Swagger UI](https://api.karumi.ai/api/v1/docs)
- [ReDoc](https://api.karumi.ai/api/v1/redoc)
- [MCP connector documentation](https://www.karumi.ai/mcp-documentation)
- [Product](https://www.karumi.ai/product)
- [Research](https://www.karumi.ai/research)
- [Blog](https://www.karumi.ai/blog)

## Embedding

- Chat Bar widget: `<script src="https://app.karumi.ai/chat.js" data-target-id="YOUR_TARGET_ID"></script>`
  Configured with `data-*` attributes; unpinned, so it always serves the latest build.

## Commercial

- [Pricing](https://www.karumi.ai/pricing): Self-Serve $900/month (1 agent, 1 language,
  3 seats, 100 demo sessions, MCP connection). Enterprise is contact-sales.
- [Sign up / log in](https://app.karumi.ai/)
- [Terms of Service](https://www.karumi.ai/terms)
- [Privacy Policy](https://www.karumi.ai/privacy)
- [DPA](https://www.karumi.ai/dpa)
- [Trust portal](https://trust.delve.co/karumi): SOC 2, ISO 27001, GDPR.

## Not published

Recorded so an agent stops looking: no llms.txt, no security.txt, no api-catalog, no A2A
agent card, no status page, no changelog, no deprecation or versioning policy, no
published rate limits, no client SDK in any package registry, no webhooks or AsyncAPI,
and no error-code reference. Errors are the FastAPI `detail` envelope, not RFC 9457.