> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kynasmith.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started

> Set up your Kynasmith account and integrate movement detection in minutes.

# Get started

Kynasmith is a movement-detection API. You author movement definitions in MoveSpec YAML, then run detection sessions that analyze pose data in real time and emit typed movement events.

There are two official SDK paths:

* **Python SDK** (`kynasmith`) for server-side, replay, and local camera workflows
* **Web SDK** (`@kynasmith/web-sdk`) for browser-side live and replay workflows

You can also use the [direct HTTP API](/api-reference/overview) from any language.

## Evaluate first

If you want to understand the product before setting up credentials, start here:

* Run the guided guest demo in the [Workbench](https://app.kynasmith.dev/workbench?demo=squat)
* Browse released public MoveSpecs in the [catalog](https://app.kynasmith.dev/catalog)
* Inspect the runtime event model in the [API reference](/api-reference/runtime-contract)

The guest Workbench is the fastest way to see validation, replay execution, and typed outputs before you commit to the full integration path.

## When you are ready to integrate

<Steps>
  <Step title="Log in to the portal">
    Go to [app.kynasmith.dev](https://app.kynasmith.dev) and sign in or create an account.
  </Step>

  <Step title="Create an organization">
    After signing in, create your organization. This is the billing and team boundary for all your projects.
  </Step>

  <Step title="Create a project">
    Inside your organization, create a project. Projects scope your MoveSpecs, detection sessions, and credentials.
  </Step>

  <Step title="Create an API key">
    Navigate to **Settings > API Keys > Create Key**. Copy the key ID and secret — you will need them to authenticate SDK and API calls.
  </Step>

  <Step title="(Browser integrations) Set up a token endpoint">
    If you plan to use the Web SDK, build a backend endpoint that exchanges your API key for a short-lived access token. See [Authentication](/get-started/authentication) for details.
  </Step>
</Steps>

## Prerequisites

* A Kynasmith evaluation path completed, or a clear target MoveSpec you want to run
* A Kynasmith project created in the portal
* A released MoveSpec version to run at detection time
* Project-bound API key credentials
* A backend token endpoint if you will call Kynasmith from the browser

## Choose an integration path

**Python SDK** — Use when your application runs on a server, worker, desktop process, or scripted local tool. See the [Python SDK quickstart](/sdks/python).

**Web SDK** — Use when your application runs in a browser and you want the SDK to own the MediaPipe browser runtime. See the [Web SDK quickstart](/sdks/web).

**Direct HTTP API** — Use when you need to integrate from another language or prefer direct API calls. See the [API reference](/api-reference/overview).

## Integration flow

<Steps>
  <Step title="Create and release a MoveSpec">
    Author MoveSpec YAML that defines the movements you want to detect. Validate the draft, create an immutable version, and release it. See [MoveSpec](/movespec/overview).
  </Step>

  <Step title="Create a detection session">
    Start a `live` or `replay` session against the released MoveSpec version.
  </Step>

  <Step title="Stream pose frames">
    The SDKs keep raw video local. They extract pose landmarks with MediaPipe and send only pose frames to Kynasmith.
  </Step>

  <Step title="Read typed events">
    Consume `event_batch`, `session_update`, and `session_done` messages until the session reaches a terminal state.
  </Step>
</Steps>