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

# Introduction

> Everything you need to build with Embeddables — install guides, configuration, and reference documentation

## Start here

Every SDK needs a project config in your repo — `projectId`, forms, experiments, and keys. Generate it locally with the **[Embeddables CLI](/reference/em-cli)** (`em login` → `em init`), then import the generated config in your app. Do not assemble that object by hand.

## Overview

SDKs are installable toolkits that connect a website or app to the Embeddables platform, each covering a single capability — visitor identity, event tracking, experimentation, form handling. This site covers installation, configuration, and usage for each one.

## Architecture

Every SDK is built around one shared foundation: **[Core](/reference/core-sdk)** resolves project and visitor identity once, and every other SDK reads that identity instead of resolving it independently.

SDKs don't depend on each other. If two capabilities need to work together — for example, an experiment assignment showing up as an analytics event — that connection is made explicitly in application code, not implicitly by the SDKs themselves. See each SDK's own page for its specific integration points.

## Available tools

<CardGroup cols={2}>
  <Card title="Core" icon="cube" href="/reference/core-sdk">
    Foundation — project and visitor identity
  </Card>

  <Card title="Analytics" icon="chart-line-up" href="/reference/sdks/analytics-sdk">
    Growth & Testing — event tracking
  </Card>

  <Card title="Experiments" icon="flask" href="/reference/sdks/experiments-sdk">
    Growth & Testing — A/B test assignment
  </Card>

  <Card title="Forms" icon="input-text" href="/reference/sdks/forms-sdk">
    Data Collection — form state, validation, and persistence
  </Card>
</CardGroup>

## Key concepts

<AccordionGroup>
  <Accordion title="Project ID">
    The unique identifier for an Embeddables project. Every SDK call is scoped to one project via
    this value.
  </Accordion>

  <Accordion title="Publishable key">
    A key in the form `pk_live_...` or `pk_sandbox_...` that authenticates requests from client-side
    code. It is safe to expose publicly — it identifies a project, it does not grant elevated
    access. Required by SDKs that call the Embeddables API, such as Analytics.

    `em init` prints sandbox and live keys for your project. You can also find them in the Embeddables admin under **[Settings → Portal / SDK](https://admin.embeddables.com/settings)** — use the sandbox key (`pk_sandbox_...`) for development and the live key (`pk_live_...`) for production.
  </Accordion>
</AccordionGroup>

Core also resolves a per-visitor identifier used across every SDK — see [App user ID](/reference/core-sdk#overview) on the Core page.

## Next steps

1. [Embeddables CLI](/reference/em-cli) — generate your project config
2. [Quickstart](/quickstart) — install Core and make your first call