Skip to main content
Karta has a small core model, but readers arrive with different jobs. Start with the path that matches the thing you need to ship, integrate, operate, or review.
If you already know the task in your own words, use the How-to index. It lists the public process questions directly, so docs search and agent retrieval can find the canonical answer.

​
Fast paths

​
By role

New agent developer

Install the CLI, scaffold an agent project, deploy it, and open the live chat page.

Existing harness user

Keep the supported harness project format you already use and add Karta’s deploy layer.

Frontend engineer

Drop in the hosted widget, customize it, and wire commands or identity later.

Backend engineer

Pick the native session API or an adapter shape your current client already speaks.

Platform or security architect

Review isolation, credentials, spend gates, audit, webhooks, and production controls.

Operator or admin

Manage keys, releases, budgets, billing, webhooks, audit, and troubleshooting.

​
Integration decisions

Make these choices before you write integration code.

​
1. How will users reach the agent?

​
2. Who is allowed to hold the credential?

  • Server-side code can hold a scoped kt_live_ API key.
  • Browsers should receive only a short-lived session token or a publishable widget key fenced by allowed origins.

​
3. What should persist?

The stable karta id selects the agent instance, workspace, and memory. Pick one karta per user, one per virtual employee, one per backend task, or one per fleet member. See Kartas & memory.

​
4. How will you operate it?

Before launch, decide who can deploy, how rollback works, what budget caps apply, which events should reach your systems, and what your support team should inspect when a session fails. Start with Production readiness and Production architecture review.